This record as markdown: /tools/mukul975-mysql-mcp-server/show-slave-status.md
What show_slave_status does on Mysql
AI agents call show_slave_status to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why show_slave_status is rated Low
This tool queries and returns replication status metadata about a MySQL slave server. It is a read-only operation that retrieves information for monitoring purposes. Although it doesn't modify data, severity is elevated to 'medium' because the exposed replication status details could reveal sensitive infrastructure topology, credentials in error messages, or lag information that could be exploited to understand…
From the tool's definition Tool name is 'show_slave_status' and description states 'Show slave status for replication.' This retrieves replication status information without modifying any data.
Attacks that exploit this kind of access
The rule that runs show_slave_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For show_slave_status, this is the rule to start with:
show_slave_status 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, apply this rule, and every show_slave_status call is checked against it from then on.
Questions about show_slave_status
Show slave status for replication. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for show_slave_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. Nothing to install.
show_slave_status 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 show_slave_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.
Set action: deny in the PolicyLayer policy for show_slave_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.
show_slave_status is provided by the Mysql MCP server (mukul975/mysql-mcp-server). 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