Return a deterministic payload after a delay that exceeds short MCP result timeouts.
AI agents call slow_lookup to retrieve information from Mcp Docs Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or returns data deterministically after a delay. It performs no mutations, deletions, or external operations. The delay is an implementation detail that affects performance but not the fundamental category of the action, which is data retrieval (Read). Severity is low because misuse would only affect response timing, not compromise data integrity or trigger unintended side effects.
From the tool's definition Tool description states it 'Return[s] a deterministic payload' - a passive retrieval operation with no data modification, deletion, or code execution.
Attacks that exploit this kind of access
Return a deterministic payload after a delay that exceeds short MCP result timeouts. It is categorised as a Read tool in the Mcp Docs Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Docs Server MCP server in PolicyLayer and add a rule for slow_lookup: 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 Docs Server. Nothing to install.
slow_lookup 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 slow_lookup 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 slow_lookup. 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.
slow_lookup is provided by the Mcp Docs Server MCP server (@mastra/mcp-docs-server). 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 →