Return the deterministic MCP reload e2e probe payload.
AI agents call reload_probe 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 a pre-computed probe payload for end-to-end testing of MCP reload functionality. It does not create, modify, delete, execute external code, or trigger state changes—it simply returns deterministic test data. This is a read-only operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states 'Return the deterministic MCP reload e2e probe payload' — a read operation that retrieves and returns a fixed payload used for testing/probing purposes. The word 'Return' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Return the deterministic MCP reload e2e probe payload. 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 reload_probe: 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.
reload_probe 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 reload_probe 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 reload_probe. 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.
reload_probe 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 →