bench_add

A other tool on the ChukMCP MCP server.

SERVERChukMCPServer SOURCEibm/chuk-mcp-server

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/ibm-chuk-mcp-server/bench-add.md

WHAT IT DOES

What bench_add does on ChukMCPServer

AI agents call bench_add as a supporting operation in ChukMCPServer workflows.

RISK

Why bench_add is rated Low

The description is empty, so classification is based on name inference. 'bench_add' most likely performs a benchmarking test of an addition operation, which has no significant side effects. Given the server context of a Python MCP framework with performance testing tools (bench_echo sibling), this is likely a read/compute operation with no external impact. Confidence is low due to missing description.

From the tool's definition Tool name is 'bench_add' but description is empty or uninformative. Based on sibling context (add, multiply, bench_echo), this is likely a benchmarking variant of an add operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bench_add safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ChukMCPServer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bench_add, this is the rule to start with:

bench_add Rate-limited

bench_add gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bench_add": {
      "limits": [
        {
          "counter": "bench_add_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ChukMCPServer, apply this rule, and every bench_add call is checked against it from then on.

FAQ

Questions about bench_add

What does the bench_add tool do? +

bench_add is a other tool on the ChukMCPServer MCP server. It is categorised as a Other tool in the ChukMCPServer MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on bench_add? +

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

What risk level is bench_add? +

bench_add is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bench_add? +

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

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

bench_add is provided by the ChukMCPServer MCP server (ibm/chuk-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ChukMCPServer, and thousands of servers like it.

This server

All 13 ChukMCPServer tools →

Across the catalogue

add on Ethereum Tools →add on Agent Jail →add on Agent Reliability Lab → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →