High Risk →

pause_routine

Pause a routine (status → paused). The routine will not run until resumed.

Part of the Agentled server.

pause_routine can trigger actions in Agentled, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AGENTLED →

Free to start. No card required.

AI agents invoke pause_routine 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.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pause_routine": {
      "limits": [
        {
          "counter": "pause_routine_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Agentled policy for all 119 tools.

Get this rule live on your own Agentled server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGENTLED →

View all 119 tools →

These attack patterns abuse exactly the kind of access pause_routine gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so pause_routine only ever does what you allow.

SECURE AGENTLED →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the pause_routine tool do? +

Pause a routine (status → paused). The routine will not run until resumed.. 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 pause_routine? +

Register the Agentled MCP server in PolicyLayer and add a rule for pause_routine: 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.

What risk level is pause_routine? +

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

Can I rate-limit pause_routine? +

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

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

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

Enforce policy on every Agentled tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.