获取服务运行时状态，包括并发限制、队列、响应限制、超时和连接状态。查询数据库前，可先查看 connections.mysql / redis / mongodb 判断启动时默认连接是否已可用。
AI agents call server_runtime_status to retrieve information from Db without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns system state information only. It has no side effects on data or operations. The description explicitly indicates it is used to check connection availability before querying databases, making it a diagnostic/informational read operation.
From the tool's definition Tool description indicates it retrieves ('获取') server runtime status, including concurrency limits, queue, response limits, timeout, and connection status. No modifications, deletions, or executions are performed.
Documented attack patterns abuse exactly the kind of access server_runtime_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for server_runtime_status:
{
"version": "1",
"default": "deny",
"tools": {
"server_runtime_status": {}
}
}server_runtime_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取服务运行时状态，包括并发限制、队列、响应限制、超时和连接状态。查询数据库前，可先查看 connections.mysql / redis / mongodb 判断启动时默认连接是否已可用。. It is categorised as a Read tool in the Db MCP Server, which means it retrieves data without modifying state.
Register the Db MCP server in PolicyLayer and add a rule for server_runtime_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 Db. Nothing to install.
server_runtime_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 server_runtime_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 server_runtime_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.
server_runtime_status is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.