Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    safenode policies

    1

    Design and generate JSON security policies for SafeNode MCP Gateway and SDKs to control AI agent actions.

    Free

    Security scanned
    safenode policies

    safenode policies

    Example session with this skill installed

    I need a SafeNode policy for my agent. It uses an MCP gateway. I want to allow file reading, but any file writes or deletes need human approval. Also, block any credit card numbers.

    • Read your context and instructions
    • Compiled the safenode policies

    I have mapped your requirements to a SafeNode policy. Since you are using the MCP Gateway, we will use context_match for the tool allowlist and redaction_metadata for sensitive data, as the gateway redacts cards before the policy engine sees them.

    SafeNode MCP Gateway Policy

    {
  "version": 1,
  "hard_rules": [
    {
      "id": "mcp-tool-allowlist",
      "type": "context_match",
      "params": {
        "context_key": "tool_name",
        "values": ["read_file", "list_directory", "search_files", "write_file", "delete_file"],
        "message": "Tool not in approved manifest."
      }
    },
    {
      "id": "block-financial-data",
      "type": "redaction_metadata",
      "params": {
        "forbidden_types": ["credit_card"],
        "message": "Action denied: payload contains credit card patterns."
      }
    }
  ],
  "soft_rules": [
    {
      "id": "review-write-delete",
      "type": "action_type_context_threshold",
      "weight": 100,
      "params": {
        "action_types": ["mcp_tool_call"],
        "context_key": "tool_name",
        "values": ["write_file", "delete_file"],
        "message": "Write or delete operations require human oversight."
      }
    }
  ],
  "default_decision": "allow"
}

    Next steps

    1. Tag tools: Ensure your gateway config includes the appropriate tool_name values for the allowlist to match.
    2. Test bands: Trigger a write_file call and verify it lands in the Review band (score 75+) in the dashboard.
    3. Monitor logs: Check the logFile for redaction_metadata hits to ensure card blocking is firing correctly.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    AI agents with tool access often pose security risks, from accidental data deletion to unauthorized financial transactions. This skill provides the logic to design and implement SafeNode policies, ensuring your agents operate within strict guardrails.

    What it does

    • Action Tiering categorizes agent tools into read-only, reversible, costly, or destructive buckets to determine baseline risk.
    • MCP Gateway Mapping handles the specific context requirements of tools behind the SafeNode gateway using tool_name and tags.
    • Rule Selection identifies the correct JSON rule types like context_match, sensitive_data, or spend_threshold for specific security goals.
    • Policy Drafting generates paste-ready JSON definitions for both hard rules (immediate denial) and soft rules (risk-based scoring).
    • Redaction Logic configures policies to act on client-side redaction metadata for credit cards and API keys.

    How it works

    1. Inventory the agent's available tools and assign them to risk tiers.
    2. Define the environment, whether using the SafeNode MCP Gateway or direct SDK integration, to determine how actions are identified.
    3. Select specific hard and soft rules based on requirements like business hours, geo-fencing, or payload inspection.
    4. Deploy the generated JSON into the SafeNode dashboard and verify against the decision log.

    Frameworks & tools

    This skill is designed for the SafeNode MCP Gateway and SafeNode SDKs. It generates JSON policy definitions compatible with the SafeNode dashboard.

    Why this beats prompting it yourself

    Generic prompts often fail to account for the technical distinction between action_type matches in SDKs versus context_match requirements in the MCP gateway. This skill applies specific patterns for redaction metadata that prevent "empty" matches on already-redacted strings.

    Use cases

    • Block Destructive Actions by creating hard-deny rules for tool patterns like delete_* or drop_*.
    • Enforce Human Review for high-cost tools like payment processing or bulk email sends based on count thresholds.
    • Prevent Data Leakage by monitoring for [REDACTED] tokens in tool arguments through redaction_metadata rules.
    • Geo-fence Agents to ensure data processing only occurs within approved cloud regions or countries.

    Known limitations

    Policies cannot detect prompt injection or agent reasoning, only the resulting tool calls. The context_match rule only supports allowlists, not individual blocks.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 2 days ago

    • Free to download with an account

    Requires

    SafeNode account
    Safenode Gateway Or A SafeNode SDK MCP

    Listed2 days ago

    What's inside

    Frequently Asked Questions