mysql_memory_usage
Show memory usage by database objects.
This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-memory-usage.md
What mysql_memory_usage does on Mysql
AI agents call mysql_memory_usage to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_memory_usage is rated Low
This tool queries and displays memory usage statistics—a non-destructive, informational operation. No data is created, modified, deleted, or executed. It belongs in the Read category with low severity because misuse would only expose internal system metrics, not cause harm to data or operations.
From the tool's definition Tool name 'mysql_memory_usage' and description 'Show memory usage by database objects' indicate a query that retrieves monitoring/diagnostic data without modifying state. The server description emphasizes 'read-only queries' and 'performance analysis'.
Attacks that exploit this kind of access
The rule that runs mysql_memory_usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_memory_usage, this is the rule to start with:
mysql_memory_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every mysql_memory_usage call is checked against it from then on.
Questions about mysql_memory_usage
Show memory usage by database objects. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_memory_usage: 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. Nothing to install.
mysql_memory_usage 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 mysql_memory_usage 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 mysql_memory_usage. 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.
mysql_memory_usage is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue