Critical Risk →

stop_stream

Stop a stream permanently and mark the job as completed. Can be called by agent or human on STREAMING or PAUSED jobs.

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

human-pages-ai/humanpages Destructive Risk 4/5

AI agents may call stop_stream to permanently remove or destroy resources in HumanPages Ai. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call stop_stream in a loop, permanently destroying resources in HumanPages Ai. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

human-pages-ai-humanpages.yaml
tools:
  stop_stream:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full HumanPages Ai policy for all 31 tools.

Tool Name stop_stream
Category Destructive
Risk Level Critical

View all 31 tools →

Agents calling destructive-class tools like stop_stream 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

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

What does the stop_stream tool do? +

Stop a stream permanently and mark the job as completed. Can be called by agent or human on STREAMING or PAUSED jobs.. It is categorised as a Destructive tool in the HumanPages Ai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on stop_stream? +

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

What risk level is stop_stream? +

stop_stream is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stop_stream? +

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

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

stop_stream is provided by the HumanPages Ai MCP server (human-pages-ai/humanpages). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on HumanPages Ai

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.