Get metrics in Prometheus format.
AI agents call mysql_metrics_prometheus to retrieve information from FastMCP MySQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metrics data and exports it in Prometheus format, which is a standard monitoring/observability operation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only gather operational metrics about the database, which is low-risk. This clearly falls under the Read category.
From the tool's definition Tool name 'mysql_metrics_prometheus' and description 'Get metrics in Prometheus format' indicate a retrieval operation with no side effects. Metrics queries are read-only operations that return monitoring data without modifying any database state.
Attacks that exploit this kind of access
Get metrics in Prometheus format. It is categorised as a Read tool in the FastMCP MySQL Server MCP Server, which means it retrieves data without modifying state.
Register the FastMCP MySQL Server MCP server in PolicyLayer and add a rule for mysql_metrics_prometheus: 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 FastMCP MySQL Server. Nothing to install.
mysql_metrics_prometheus 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 mysql_metrics_prometheus 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 mysql_metrics_prometheus. 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.
mysql_metrics_prometheus is provided by the FastMCP MySQL Server MCP server (jinto/fastmcp-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →