Track MCP server performance: call counts, error rates, most used tools.
AI agents call mcp_performance to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays observability metrics (call counts, error rates, tool usage statistics) about MCP server performance. It is purely a read/query operation with no side effects, data modification, or destructive actions. Misuse potential is minimal as it only surfaces existing telemetry data.
From the tool's definition Track MCP server performance: call counts, error rates, most used tools
Documented attack patterns abuse exactly the kind of access mcp_performance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_performance:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_performance": {}
}
} mcp_performance 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.
Track MCP server performance: call counts, error rates, most used tools. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for mcp_performance: 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 Claude Code Toolkit. Nothing to install.
mcp_performance 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 mcp_performance 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 mcp_performance. 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.
mcp_performance is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.