performance.evaluate_throughput_scaling

WHAT IT DOES

What performance.evaluate_throughput_scaling does on ContextForge MCP Gateway

AI agents invoke performance.evaluate_throughput_scaling 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 performance.evaluate_throughput_scaling needs a policy

This tool executes live load/stress tests against the MCP gateway by firing concurrent requests, which constitutes running an external operation whose effects depend on arguments (e.g., concurrency level, duration). It could degrade service availability or exhaust rate limits if misused, warranting medium severity. It does not persist data or move money, so Execute is the most appropriate category.

From the tool's definition 'Test concurrent request handling and scaling behavior' — actively runs concurrent requests against the gateway to measure throughput and scaling

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

performance.evaluate_throughput_scaling Rate-limited

performance.evaluate_throughput_scaling 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.evaluate_throughput_scaling": {
      "limits": [
        {
          "counter": "performance.evaluate_throughput_scaling_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 performance.evaluate_throughput_scaling

What does the performance.evaluate_throughput_scaling tool do? +

Test concurrent request handling and scaling behavior. 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 performance.evaluate_throughput_scaling? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for performance.evaluate_throughput_scaling: 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 performance.evaluate_throughput_scaling? +

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

Can I rate-limit performance.evaluate_throughput_scaling? +

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

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

performance.evaluate_throughput_scaling 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.