create_security_policy · Claude MCP Server Integration MCP

WHAT IT DOES

What create_security_policy does on Claude MCP Server Integration

AI agents use create_security_policy to create or update resources in Claude MCP Server Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude MCP Server Integration environment.

WHY IT NEEDS A POLICY

Why create_security_policy needs a policy

Creating a security policy is a reversible write operation that modifies configuration state. It is not destructive (policies can be updated or removed), not financial, and not code execution per se. However, severity is elevated to 'high' because misconfigured security policies could weaken system protection or lock users out, making it a high-impact write operation.

From the tool's definition Tool name 'create_security_policy' and description 'セキュリティポリシーを作成します' (creates a security policy) indicate data creation. This modifies system configuration/policy state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_security_policy Rate-limited

create_security_policy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_security_policy": {
      "limits": [
        {
          "counter": "create_security_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude MCP Server Integration, so you can run agents against it safely.

FAQ

Questions about create_security_policy

What does the create_security_policy tool do? +

セキュリティポリシーを作成します. It is categorised as a Write tool in the Claude MCP Server Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_security_policy? +

Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for create_security_policy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude MCP Server Integration. Nothing to install.

What risk level is create_security_policy? +

create_security_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_security_policy? +

Yes. Add a rate_limit block to the create_security_policy rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block create_security_policy completely? +

Set action: deny in the PolicyLayer policy for create_security_policy. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides create_security_policy? +

create_security_policy is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.