performance_analysis · Claude Jester MCP: Risk & Policy

WHAT IT DOES

What performance_analysis does on Claude Jester MCP

AI agents invoke performance_analysis to trigger actions in Claude Jester MCP. 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 performance_analysis needs a policy

Performance benchmarking inherently requires executing code to measure runtime characteristics. Given this tool lives on a server explicitly designed for code execution and optimization, it almost certainly runs code in the execution environment.

From the tool's definition 'performance analysis with benchmarking' implies running/executing code to measure performance metrics, situated alongside 'execute_code' and 'optimize_code' tools in a 'secure execution environment'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

performance_analysis Rate-limited

performance_analysis 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": {
    "performance_analysis": {
      "limits": [
        {
          "counter": "performance_analysis_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 Claude Jester MCP, so you can run agents against it safely.

FAQ

Questions about performance_analysis

What does the performance_analysis tool do? +

Detailed performance analysis with benchmarking and optimization recommendations. It is categorised as a Execute tool in the Claude Jester MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on performance_analysis? +

Register the Claude Jester MCP server in PolicyLayer and add a rule for performance_analysis: 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 Jester MCP. Nothing to install.

What risk level is performance_analysis? +

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

Can I rate-limit performance_analysis? +

Yes. Add a rate_limit block to the performance_analysis 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 performance_analysis completely? +

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

performance_analysis is provided by the Claude Jester MCP server (mstanton/claude-jester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.