archive_identity · PostIdentity MCP Server MCP

WHAT IT DOES

What archive_identity does on PostIdentity MCP Server

AI agents use archive_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 archive_identity needs a policy

Archiving is a Write operation because it modifies data (marks an identity as archived) but is explicitly reversible ('can be restored later'). It does not permanently delete data, so it is not Destructive. Severity is medium because misuse could hide or disable social media identities, affecting the user's ability to operate accounts, but the reversibility and lack of permanent loss limits impact.

From the tool's definition Tool name 'archive_identity' and description states it 'Archive an identity (can be restored later from Settings)', indicating a reversible modification to state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_identity Rate-limited

archive_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": {
    "archive_identity": {
      "limits": [
        {
          "counter": "archive_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 archive_identity

What does the archive_identity tool do? +

Archive an identity (can be restored later from Settings). 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 archive_identity? +

Register the PostIdentity MCP Server MCP server in PolicyLayer and add a rule for archive_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 archive_identity? +

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

Can I rate-limit archive_identity? +

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

Set action: deny in the PolicyLayer policy for archive_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 archive_identity? +

archive_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.