Low Risk

get_caller_identity

Returns the authenticated identity of the calling agent. If you connected with ERC-8128 signed requests, this resolves your wallet address to your ENS name, agent metadata, and portfolio summary. Call this first to confirm your identity is recognized. Requires ERC-8128 authentication (signed HTT...

Part of the Name Whisper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_caller_identity to retrieve information from Name Whisper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_caller_identity only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

namewhisper-ens-tools.yaml
tools:
  get_caller_identity:
    rules:
      - action: allow

See the full Name Whisper policy for all 34 tools.

Tool Name get_caller_identity
Category Read
Risk Level Low

View all 34 tools →

Agents calling read-class tools like get_caller_identity have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_caller_identity tool do? +

Returns the authenticated identity of the calling agent. If you connected with ERC-8128 signed requests, this resolves your wallet address to your ENS name, agent metadata, and portfolio summary. Call this first to confirm your identity is recognized. Requires ERC-8128 authentication (signed HTTP requests). See GET /mcp/auth for setup details.. It is categorised as a Read tool in the Name Whisper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_caller_identity? +

Add a rule in your Intercept YAML policy under the tools section for get_caller_identity. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Name Whisper MCP server.

What risk level is get_caller_identity? +

get_caller_identity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_caller_identity? +

Yes. Add a rate_limit block to the get_caller_identity rule in your Intercept 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 get_caller_identity completely? +

Set action: deny in the Intercept policy for get_caller_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 get_caller_identity? +

get_caller_identity is provided by the Name Whisper MCP server (namewhisper/ens-tools). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Name Whisper

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.