tool_bench_setup_requirements · Frappe MCP Server MCP

WHAT IT DOES

What tool_bench_setup_requirements does on Frappe MCP Server

AI agents invoke tool_bench_setup_requirements 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_setup_requirements needs a policy

Based on the name, this tool likely runs package installation commands (e.g., pip install -r requirements.txt) to set up dependencies for a Frappe bench. This constitutes executing external operations/commands on the system. The empty description lowers confidence, but the server context (managing Frappe benches, running scripts) and the naming pattern strongly suggest an execution action.

From the tool's definition Tool name 'tool_bench_setup_requirements' suggests installing/setting up dependencies; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_bench_setup_requirements Rate-limited

tool_bench_setup_requirements 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_setup_requirements": {
      "limits": [
        {
          "counter": "tool_bench_setup_requirements_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_setup_requirements

What does the tool_bench_setup_requirements tool do? +

tool_bench_setup_requirements. 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_setup_requirements? +

Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for tool_bench_setup_requirements: 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_setup_requirements? +

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

Can I rate-limit tool_bench_setup_requirements? +

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

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

tool_bench_setup_requirements 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.