tool_bench_start · Frappe MCP Server MCP: Risk & Policy

WHAT IT DOES

What tool_bench_start does on Frappe MCP Server

AI agents invoke tool_bench_start to trigger actions in Frappe 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 tool_bench_start needs a policy

Starting bench services is an Execute action because it triggers external operations (service startup) whose effects depend on the bench configuration and system state. While not destructive or financial, it can disrupt operations or expose the system if misconfigured. The high severity reflects the potential for service outages or unintended side effects.

From the tool's definition Server description states the tool enables 'restarting services' and tool name 'tool_bench_start' indicates starting/launching bench services. The Frappe bench is a development framework that runs application servers and processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_bench_start Rate-limited

tool_bench_start 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": {
    "tool_bench_start": {
      "limits": [
        {
          "counter": "tool_bench_start_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 Frappe MCP Server, so you can run agents against it safely.

FAQ

Questions about tool_bench_start

What does the tool_bench_start tool do? +

tool_bench_start. It is categorised as a Execute tool in the Frappe 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 tool_bench_start? +

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

What risk level is tool_bench_start? +

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

Can I rate-limit tool_bench_start? +

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

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

tool_bench_start is provided by the Frappe MCP Server MCP server (kallusuvaidyam/frappe_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.