update_agent_identity · Tether Name MCP: Risk & Policy

WHAT IT DOES

What update_agent_identity does on Tether Name

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

WHY IT NEEDS A POLICY

Why update_agent_identity needs a policy

This tool modifies existing agent identity metadata reversibly. It changes which identity is displayed for an agent verification but does not delete data (ruling out Destructive), execute arbitrary code (ruling out Execute), or move funds (ruling out Financial).

From the tool's definition Tool name contains 'update' and description states 'Update which identity is shown when an agent is verified', indicating modification of an agent's identity configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_agent_identity Rate-limited

update_agent_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": {
    "update_agent_identity": {
      "limits": [
        {
          "counter": "update_agent_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 Tether Name, so you can run agents against it safely.

FAQ

Questions about update_agent_identity

What does the update_agent_identity tool do? +

Update which identity is shown when an agent is verified. Use a verified domainId to show that domain, or set showEmail=true to show account email. It is categorised as a Write tool in the Tether Name MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_agent_identity? +

Register the Tether Name MCP server in PolicyLayer and add a rule for update_agent_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 Tether Name. Nothing to install.

What risk level is update_agent_identity? +

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

Can I rate-limit update_agent_identity? +

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

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

update_agent_identity is provided by the Tether Name MCP server (tether-name-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.