agent.benchmark_performance · ContextForge MCP Gateway MCP

WHAT IT DOES

What agent.benchmark_performance does on ContextForge MCP Gateway

AI agents invoke agent.benchmark_performance to trigger actions in ContextForge MCP Gateway. 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 agent.benchmark_performance needs a policy

This tool executes benchmarking operations, which involve running test code and triggering external performance measurement workflows. While benchmarking is typically read-like in intent (gathering metrics), the actual execution of benchmarks constitutes code execution whose side effects (resource consumption, timing measurements, state changes) depend on the benchmark parameters provided.

From the tool's definition Tool name contains 'run' semantic (benchmark_performance implies execution): 'Run comprehensive agent benchmarks' in the description explicitly indicates code/operation execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agent.benchmark_performance Rate-limited

agent.benchmark_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": {
    "agent.benchmark_performance": {
      "limits": [
        {
          "counter": "agent.benchmark_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 ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about agent.benchmark_performance

What does the agent.benchmark_performance tool do? +

Run comprehensive agent benchmarks comparing against baselines. It is categorised as a Execute tool in the ContextForge MCP Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on agent.benchmark_performance? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for agent.benchmark_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 ContextForge MCP Gateway. Nothing to install.

What risk level is agent.benchmark_performance? +

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

Can I rate-limit agent.benchmark_performance? +

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

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

agent.benchmark_performance is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.