Show the MySQL process list (running connections and their current queries).
AI agents call list_processes 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.
This tool retrieves and displays the MySQL process list, which is informational data about active connections and their current queries. It has no side effects, does not modify data, execute code, delete anything, or move money. It is purely a read operation for diagnostic/monitoring purposes.
From the tool's definition Tool name 'list_processes' and description 'Show the MySQL process list' indicates retrieval of running connection and query information with no modification or execution capability.
Attacks that exploit this kind of access
Show the MySQL process list (running connections and their current queries). 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 list_processes: 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.
list_processes 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 list_processes 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 list_processes. 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.
list_processes 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 →