mysql_event_status

Get detailed status and execution history for a specific event.

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

What mysql_event_status does on Mysql Mcp

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

This tool retrieves and queries information about MySQL events (automated scheduled tasks) and their execution history. It performs a read-only operation that returns status data without creating, modifying, deleting, or executing any database operations. The use of 'Get' in the description confirms a read action. There is no indication of side effects or state changes.

From the tool's definition Tool name 'mysql_event_status' and description 'Get detailed status and execution history for a specific event' indicate retrieval of event metadata and historical data with no modification capability.

Questions about mysql_event_status

What does the mysql_event_status tool do? +

Get detailed status and execution history for a specific event. 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_event_status? +

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

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

Can I rate-limit mysql_event_status? +

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

Set action: deny in the PolicyLayer policy for mysql_event_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_event_status? +

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