mysql_scheduler_status

Get the global Event Scheduler status and event statistics.

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-scheduler-status.md

What mysql_scheduler_status does on Mysql Mcp

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

This tool retrieves the current status of MySQL's Event Scheduler and associated statistics. The verb 'Get' and context of 'status' and 'statistics' clearly indicate a read-only operation with no data modification, code execution, or destructive capability. It is purely informational and has no blast radius beyond information disclosure.

From the tool's definition Tool name 'mysql_scheduler_status' and description 'Get the global Event Scheduler status and event statistics' indicate a query/retrieval operation that returns status information and statistics without modification or side effects.

Questions about mysql_scheduler_status

What does the mysql_scheduler_status tool do? +

Get the global Event Scheduler status and event statistics. 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_scheduler_status? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_scheduler_status: 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_scheduler_status? +

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

Can I rate-limit mysql_scheduler_status? +

Yes. Add a rate_limit block to the mysql_scheduler_status 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_scheduler_status completely? +

Set action: deny in the PolicyLayer policy for mysql_scheduler_status. 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_scheduler_status? +

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

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