Return a deterministic payload from a headless MCP tool.
AI agents call delayed_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 and returns data ('deterministic payload') without modifying, executing external operations, or causing destructive effects. While the description is somewhat vague, 'delayed_lookup' in a documentation server context most closely aligns with Read operations like fetch or get. The deterministic nature suggests a pure function with no side effects.
From the tool's definition Tool description states 'Return a deterministic payload' which indicates data retrieval with no side effects. The tool name 'delayed_lookup' and context of accessing documentation suggests a read-only query operation.
Attacks that exploit this kind of access
Return a deterministic payload from a headless MCP tool. 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 delayed_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.
delayed_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 delayed_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 delayed_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.
delayed_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 →