run_tool

Dispatch any Easybits tool by name — even tools NOT loaded in the active toolGroup. Use this after

SERVEREasyBits SOURCE@easybits.cloud/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/run-tool.md

WHAT IT DOES

What run_tool does on EasyBits

AI agents invoke run_tool to trigger actions in EasyBits. 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.

RISK

Why run_tool is rated High

Enables arbitrary execution of unvetted tools including destructive operations without explicit loading or authorization.

From the tool's definition Dispatch any Easybits tool by name — even tools NOT loaded in active toolGroup.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_tool safely

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

run_tool Rate-limited

run_tool 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": {
    "run_tool": {
      "limits": [
        {
          "counter": "run_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about run_tool

What does the run_tool tool do? +

Dispatch any Easybits tool by name — even tools NOT loaded in the active toolGroup. Use this after. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_tool? +

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

What risk level is run_tool? +

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

Can I rate-limit run_tool? +

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

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

run_tool is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →