AI agents call get_agent_contact_status to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only information retrieval tool that returns the status of an agent's contact verification state. It has no side effects, does not modify any data, and does not trigger external operations. The blast radius of misuse is minimal—an attacker could learn an agent's verification status but cannot escalate privileges, modify systems, or commit financial obligations through this tool alone.
From the tool's definition Tool name 'get_agent_contact_status' and description indicate it retrieves/queries the current contact assurance state of an agent (wallet_only, email_pending, email_verified, passkey_pending, or operator_passkey).
Attacks that exploit this kind of access
Get the current agent contact assurance state: wallet_only, email_pending, email_verified, passkey_pending, or operator_passkey. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for get_agent_contact_status: 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 Run402. Nothing to install.
get_agent_contact_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_agent_contact_status 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.
Set action: deny in the PolicyLayer policy for get_agent_contact_status. 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.
get_agent_contact_status is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_agent_contact_status is one line of Run402's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →