proxysql_memory_stats
Get ProxySQL memory usage metrics from stats_memory_metrics. Shows memory for SQLite, auth, query digests, and more.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-memory-stats.md
What proxysql_memory_stats does on Mysql Mcp
AI agents call proxysql_memory_stats to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why proxysql_memory_stats is rated Low
This tool queries and retrieves memory statistics from ProxySQL's stats_memory_metrics table. It performs a read-only operation to display metrics about memory usage (SQLite, auth, query digests). There are no side effects, data modifications, deletions, or external operations triggered. It is purely observational/diagnostic in nature, fitting the 'Read' category of data retrieval with no side effects.
From the tool's definition Tool name 'proxysql_memory_stats' and description 'Get ProxySQL memory usage metrics' indicate retrieval of monitoring/diagnostic data with no modification capability.
Attacks that exploit this kind of access
The rule that runs proxysql_memory_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxysql_memory_stats, this is the rule to start with:
proxysql_memory_stats 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 Mcp, apply this rule, and every proxysql_memory_stats call is checked against it from then on.
Questions about proxysql_memory_stats
Get ProxySQL memory usage metrics from stats_memory_metrics. Shows memory for SQLite, auth, query digests, and more. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for proxysql_memory_stats: 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. Nothing to install.
proxysql_memory_stats 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 proxysql_memory_stats 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 proxysql_memory_stats. 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.
proxysql_memory_stats is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). 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