Return the deterministic MCP reload e2e probe payload.
AI agents call reload_probe 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 a deterministic probe payload, which is a testing/diagnostic artifact. It performs no modifications, deletions, or external operations; it simply returns data. This is a Read operation with low severity since it only provides test probe information and cannot affect production systems or data.
From the tool's definition Tool name is 'reload_probe' and description states it 'Return[s] the deterministic MCP reload e2e probe payload' — this retrieves/returns a pre-computed test payload 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 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 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 Registry Registry. 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 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 →