🔍 Debug retrieval queries with pipeline tracing, similarity scores, and expected/actual comparison. Diagnose why queries don
AI agents call indexfoundry_debug_query to retrieve information from IndexFoundry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes internal pipeline metrics and query results for diagnostic purposes. It traces retrieval queries and compares expected vs actual results, which is fundamentally a read-only diagnostic operation. There is no indication of data mutation, code execution, or irreversible actions.
From the tool's definition Tool name indicates debugging functionality (debug_query), description emphasizes diagnostic operations (tracing, similarity scores, comparison) with no mention of data modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
🔍 Debug retrieval queries with pipeline tracing, similarity scores, and expected/actual comparison. Diagnose why queries don. It is categorised as a Read tool in the IndexFoundry MCP MCP Server, which means it retrieves data without modifying state.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_debug_query: 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 IndexFoundry MCP. Nothing to install.
indexfoundry_debug_query 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 indexfoundry_debug_query 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 indexfoundry_debug_query. 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.
indexfoundry_debug_query is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). 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 →