Return the deterministic Mastra Code MCP HTTP e2e status payload.
AI agents call lookup_status to retrieve information from Mcp Registry Registry without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns a status payload—a read-only query operation. There is no indication of data creation, modification, deletion, code execution, or financial impact. The deterministic nature and focus on returning a payload confirms this is a simple data retrieval operation.
From the tool's definition Tool name 'lookup_status' and description 'Return the deterministic Mastra Code MCP HTTP e2e status payload' indicate retrieval of status information with no modification or execution of side effects.
Attacks that exploit this kind of access
Return the deterministic Mastra Code MCP HTTP e2e status payload. It is categorised as a Read tool in the Mcp Registry Registry MCP Server, which means it retrieves data without modifying state.
Register the Mcp Registry Registry MCP server in PolicyLayer and add a rule for lookup_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 Mcp Registry Registry. Nothing to install.
lookup_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 lookup_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 lookup_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.
lookup_status is provided by the Mcp Registry Registry MCP server (@mastra/mcp-registry-registry). 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 →