Raw
AI agents call innodb_status to retrieve information from Querybridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
InnoDB status commands retrieve internal database engine state and diagnostics without side effects. This is a non-destructive information retrieval operation. The minimal description ('Raw') suggests direct status output without parameterization. Low severity because the blast radius of misuse is limited to information disclosure of database internals, not data destruction or financial impact.
From the tool's definition Tool named 'innodb_status' with description 'Raw' suggests retrieval of InnoDB engine status/diagnostics. The name pattern and server context (MySQL database operations) indicate a read-only diagnostic query. No modification or execution capabilities implied.
Attacks that exploit this kind of access
Raw. It is categorised as a Read tool in the Querybridge MCP Server, which means it retrieves data without modifying state.
Register the Querybridge MCP server in PolicyLayer and add a rule for innodb_status: 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 Querybridge. Nothing to install.
innodb_status 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 innodb_status 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 innodb_status. 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.
innodb_status is provided by the Querybridge MCP server (mahmoudhassanmustafa/querybridge-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 →