mysql_sys_user_summary

Get user activity summary including statements, connections, and latency from sys schema.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-sys-user-summary.md

What mysql_sys_user_summary does on Mysql Mcp

AI agents call mysql_sys_user_summary 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 mysql_sys_user_summary is rated Low

This tool queries the MySQL sys schema to retrieve diagnostic and monitoring information about user activity. It has no side effects, does not modify data, does not execute code, and does not delete anything. It is purely informational/observational in nature. The low severity reflects that misuse would only expose existing user activity metrics, not cause damage or enable further attacks independently.

From the tool's definition Tool retrieves user activity summary data from sys schema including statements, connections, and latency. Keywords: 'Get' and 'summary' indicate data retrieval with no modification or execution capability.

Questions about mysql_sys_user_summary

What does the mysql_sys_user_summary tool do? +

Get user activity summary including statements, connections, and latency from sys schema. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_sys_user_summary? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_sys_user_summary: 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.

What risk level is mysql_sys_user_summary? +

mysql_sys_user_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_sys_user_summary? +

Yes. Add a rate_limit block to the mysql_sys_user_summary 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.

How do I block mysql_sys_user_summary completely? +

Set action: deny in the PolicyLayer policy for mysql_sys_user_summary. 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.

What MCP server provides mysql_sys_user_summary? +

mysql_sys_user_summary 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mysql's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.