create_identity · PostIdentity MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_identity does on PostIdentity MCP Server

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

WHY IT NEEDS A POLICY

Why create_identity needs a policy

This tool creates new data (an identity profile) that can be modified, updated, or deleted later (as evidenced by sibling tools like archive_identity and generate_post). It does not retrieve/query data (Read), execute arbitrary code (Execute), permanently destroy data (Destructive), or involve financial transactions (Financial).

From the tool's definition Tool description states 'Create a new identity' which is explicitly a creation operation that modifies data reversibly. The tool creates a new identity resource in the PostIdentity system based on provided input (description and example posts).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_identity Rate-limited

create_identity 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_identity": {
      "limits": [
        {
          "counter": "create_identity_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 PostIdentity MCP Server, so you can run agents against it safely.

FAQ

Questions about create_identity

What does the create_identity tool do? +

Create a new identity from a description and example posts. It is categorised as a Write tool in the PostIdentity MCP Server 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_identity? +

Register the PostIdentity MCP Server MCP server in PolicyLayer and add a rule for create_identity: 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 PostIdentity MCP Server. Nothing to install.

What risk level is create_identity? +

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

Can I rate-limit create_identity? +

Yes. Add a rate_limit block to the create_identity 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_identity completely? +

Set action: deny in the PolicyLayer policy for create_identity. 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_identity? +

create_identity is provided by the PostIdentity MCP Server MCP server (postidentity/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.