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 ou...
Part of the Agentled server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"do": {
"limits": [
{
"counter": "do_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Agentled policy for all 119 tools.
These attack patterns abuse exactly the kind of access do gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Agentled MCP server in PolicyLayer and add a rule for do: 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 Agentled. Nothing to install.
do is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the do 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.
Set action: deny in the PolicyLayer 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.
do is provided by the Agentled MCP server (@agentled/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 119 Agentled tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.