mysql_replication_status

Show replication slave/replica status. Use summary=true for key metrics only.

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

WHAT IT DOES

What mysql_replication_status does on Mysql Mcp

AI agents call mysql_replication_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.

RISK

Why mysql_replication_status is rated Low

This tool retrieves and displays the replication status of MySQL slaves/replicas. It has no side effects—it only reads and reports on the current state of replication without modifying any data, configurations, or system behavior. The mention of summary parameters confirms it is a read-only diagnostic tool.

From the tool's definition Tool name contains 'status' and description states 'Show replication slave/replica status', which is a query/display operation. The summary parameter allows filtering to 'key metrics only', indicating a retrieval function with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_replication_status 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 mysql_replication_status, this is the rule to start with:

mysql_replication_status Allowed

mysql_replication_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_replication_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_replication_status call is checked against it from then on.

FAQ

Questions about mysql_replication_status

What does the mysql_replication_status tool do? +

Show replication slave/replica status. Use summary=true for key metrics only. 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_replication_status? +

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

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

Can I rate-limit mysql_replication_status? +

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

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

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

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →