SHOW FULL PROCESSLIST（行数上限 MYSQL_MCP_PROCESS_LIST_MAX，默认 100）；需 PROCESS 权限
AI agents call process_list to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
SHOW PROCESSLIST is a diagnostic query that retrieves metadata about active MySQL connections and processes without modifying any data. It has no side effects, does not alter database state, and serves only to list/query existing process information.
From the tool's definition Tool executes 'SHOW FULL PROCESSLIST' which retrieves process and connection information from MySQL. The description explicitly states it displays process list data (with a row limit of MYSQL_MCP_PROCESS_LIST_MAX, default 100) and requires PROCESS privilege.
Attacks that exploit this kind of access
SHOW FULL PROCESSLIST（行数上限 MYSQL_MCP_PROCESS_LIST_MAX，默认 100）；需 PROCESS 权限. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for process_list: 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 MySQL MCP Server. Nothing to install.
process_list 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 process_list 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 process_list. 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.
process_list is provided by the MySQL MCP Server MCP server (yclenove/mysql-mcp-server). 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 →