Get agent ID from a registration transaction hash (recovery tool).
AI agents call get_agent_id_from_tx to retrieve information from Basis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves an agent ID based on a transaction hash input. It performs a lookup operation without modifying, creating, deleting, or executing any actions. The 'recovery tool' designation further confirms it is informational in nature. No state changes, financial transactions, or destructive operations are involved.
From the tool's definition Tool description states 'Get agent ID from a registration transaction hash (recovery tool)' - the verb 'Get' and framing as a 'recovery tool' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Get agent ID from a registration transaction hash (recovery tool). It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_agent_id_from_tx: 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 Basis MCP Server. Nothing to install.
get_agent_id_from_tx 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_id_from_tx 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_id_from_tx. 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_id_from_tx is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →