diagnose_performance · KYC MCP Server MCP: Risk & Policy

WHAT IT DOES

What diagnose_performance does on KYC MCP Server

AI agents invoke diagnose_performance to trigger actions in KYC MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why diagnose_performance needs a policy

Although this tool retrieves diagnostic results rather than modifying system state, the act of 'running diagnostics' constitutes executing operations on the system. The severity is medium because diagnostic tools typically have read-only side effects (they observe system behavior) but could potentially trigger resource-intensive operations, slow the system, or expose sensitive diagnostic data.

From the tool's definition Tool performs 'run performance diagnostics' which involves executing diagnostic operations on the system. The verb 'run' and 'diagnose' indicate active system operations rather than passive data retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_performance Rate-limited

diagnose_performance stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "diagnose_performance": {
      "limits": [
        {
          "counter": "diagnose_performance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches KYC MCP Server, so you can run agents against it safely.

FAQ

Questions about diagnose_performance

What does the diagnose_performance tool do? +

Run performance diagnostics and identify bottlenecks. It is categorised as a Execute tool in the KYC MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnose_performance? +

Register the KYC MCP Server MCP server in PolicyLayer and add a rule for diagnose_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 KYC MCP Server. Nothing to install.

What risk level is diagnose_performance? +

diagnose_performance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit diagnose_performance? +

Yes. Add a rate_limit block to the diagnose_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.

How do I block diagnose_performance completely? +

Set action: deny in the PolicyLayer policy for diagnose_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.

What MCP server provides diagnose_performance? +

diagnose_performance is provided by the KYC MCP Server MCP server (vishnurudra-ai/kyc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.