High Risk →

do

Semantic intent router — describe what you want to accomplish in plain English and Agentled will find the best matching live workflow in your workspace. Optionally auto-executes the matched workflow. Examples: - "find the CEO's email for stripe.com" - "research acme corp and score them again...

Part of the Agentled MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@agentled/mcp-server Execute Risk 3/5

AI agents invoke do to trigger processes or run actions in Agentled. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

do can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-agentled-mcp-server.yaml
tools:
  do:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Agentled policy for all 56 tools.

Tool Name do
Category Execute
MCP Server Agentled MCP Server
Risk Level High

View all 56 tools →

Agents calling execute-class tools like do have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

do is one of the high-risk operations in Agentled. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the do tool do? +

Semantic intent router — describe what you want to accomplish in plain English and Agentled will find the best matching live workflow in your workspace. Optionally auto-executes the matched workflow. Examples: - "find the CEO's email for stripe.com" - "research acme corp and score them against our ICP" - "scrape https://example.com and summarize it" Returns the best match with confidence score, extracted inputs, and alternatives. Set execute=true to also start the matched workflow immediately.. It is categorised as a Execute tool in the Agentled MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on do? +

Add a rule in your Intercept YAML policy under the tools section for do. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentled MCP server.

What risk level is do? +

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

Can I rate-limit do? +

Yes. Add a rate_limit block to the do rule in your Intercept 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 do completely? +

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

do is provided by the Agentled MCP server (@agentled/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Agentled

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.