Pauses the streaming for the given invoice
AI agents invoke pauseStreamingTool to trigger actions in Beep MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pausing a streaming session is an external operation with side effects on an active session/invoice. While it may be reversible (streaming can be resumed), it interrupts an ongoing service tied to payments. It falls under Execute as it triggers an external platform operation, not purely Financial since it doesn't directly move money, but has financial implications given the invoice context.
From the tool's definition 'Pauses the streaming for the given invoice' — triggers an external operation (pausing a streaming session) on the Beep platform tied to a financial invoice
Attacks that exploit this kind of access
Pauses the streaming for the given invoice. It is categorised as a Execute tool in the Beep MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Beep MCP Server MCP server in PolicyLayer and add a rule for pauseStreamingTool: 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 Beep MCP Server. Nothing to install.
pauseStreamingTool 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 pauseStreamingTool 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 pauseStreamingTool. 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.
pauseStreamingTool is provided by the Beep MCP Server MCP server (lamdanghoang/beep-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →