Benchmark response latency for all configured MCP servers
AI agents call bench to retrieve information from Mcp Doctor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool measures and reports performance metrics (response latency) for MCP servers. It is a read/diagnostic operation with no side effects — it queries servers to measure timing but does not create, modify, delete, or execute anything with lasting impact.
From the tool's definition Benchmark response latency for all configured MCP servers
Attacks that exploit this kind of access
Benchmark response latency for all configured MCP servers. It is categorised as a Read tool in the Mcp Doctor MCP Server, which means it retrieves data without modifying state.
Register the Mcp Doctor MCP server in PolicyLayer and add a rule for bench: 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 Mcp Doctor. Nothing to install.
bench 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 bench 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 bench. 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.
bench is provided by the Mcp Doctor MCP server (realwigu/mcp-doctor). 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 →