Low Risk

decide_interrupt

Submit a human decision on an interrupt request (approve or reject).

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

AI agents call decide_interrupt to retrieve information from Loopin without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though decide_interrupt only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

nicholasemccormick-loopin-mcp.yaml
tools:
  decide_interrupt:
    rules:
      - action: allow

See the full Loopin policy for all 6 tools.

Tool Name decide_interrupt
Category Read
MCP Server Loopin MCP Server
Risk Level Low

Agents calling read-class tools like decide_interrupt 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 Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the decide_interrupt tool do? +

Submit a human decision on an interrupt request (approve or reject).. It is categorised as a Read tool in the Loopin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on decide_interrupt? +

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

What risk level is decide_interrupt? +

decide_interrupt is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit decide_interrupt? +

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

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

decide_interrupt is provided by the Loopin MCP server (nicholasemccormick/loopin-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Loopin

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.