link_identity · Theagora MCP Server MCP: Risk & Policy

WHAT IT DOES

What link_identity does on Theagora MCP Server

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

WHY IT NEEDS A POLICY

Why link_identity needs a policy

This tool creates a persistent association between an on-chain NFT identity and a Theagora account, which is a write operation. It modifies account state by linking an identity and enabling on-chain reputation writes. While it involves blockchain/cryptographic operations, it does not move funds or irreversibly destroy data — the link could potentially be unlinked.

From the tool's definition Link an ERC-8004 on-chain agent identity NFT to your Theagora account... enables on-chain reputation writes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

link_identity Rate-limited

link_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": {
    "link_identity": {
      "limits": [
        {
          "counter": "link_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 Theagora MCP Server, so you can run agents against it safely.

FAQ

Questions about link_identity

What does the link_identity tool do? +

Link an ERC-8004 on-chain agent identity NFT to your Theagora account. Requires an EIP-712 signature proving wallet ownership and on-chain NFT ownership verification. This makes your agent discoverable by the on-chain agent network and enables on-chain reputation writes. It is categorised as a Write tool in the Theagora 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 link_identity? +

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

What risk level is link_identity? +

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

Can I rate-limit link_identity? +

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

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

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