Show the query execution plan without executing the query. Set analyze=true to actually run the query and get real timing data instead of estimates (PostgreSQL/MySQL). Always allowed regardless of permission level.
AI agents call explain_query to retrieve information from Omnibase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the execution plan for a query but does not execute it against data. Even with analyze=true, it only gathers timing/planning metadata rather than modifying any data. It is explicitly described as always allowed and read-only in nature.
From the tool's definition 'Show the query execution plan without executing the query' and 'Always allowed regardless of permission level'
Attacks that exploit this kind of access
Show the query execution plan without executing the query. Set analyze=true to actually run the query and get real timing data instead of estimates (PostgreSQL/MySQL). Always allowed regardless of permission level. It is categorised as a Read tool in the Omnibase MCP Server, which means it retrieves data without modifying state.
Register the Omnibase MCP server in PolicyLayer and add a rule for explain_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 Omnibase. Nothing to install.
explain_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 explain_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 explain_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.
explain_query is provided by the Omnibase MCP server (omnibase-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 →