[cost: free (pure CPU, no network) | read-only] Return a hand-curated SIP scenario as a Mermaid sequenceDiagram plus a bullet list of step-by-step explanations with RFC references. Use this when the user asks 'show me what X looks like' and you don't have a real trace handy. Available scenarios: ...
Part of the SIPFlow server.
Free to start. No card required.
AI agents may call sip_ladder_example to permanently remove or destroy resources in SIPFlow. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call sip_ladder_example in a loop, permanently destroying resources in SIPFlow. There is no undo for destructive operations. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"sip_ladder_example"
]
}See the full SIPFlow policy for all 21 tools.
These attack patterns abuse exactly the kind of access sip_ladder_example gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
[cost: free (pure CPU, no network) | read-only] Return a hand-curated SIP scenario as a Mermaid sequenceDiagram plus a bullet list of step-by-step explanations with RFC references. Use this when the user asks 'show me what X looks like' and you don't have a real trace handy. Available scenarios: basic-call, auth-challenge, cancel-before-answer, early-media, hold-resume, refer-blind, proxy-with-record-route, shaken-attested-invite, bye-glare, redirect-302. Pair with: search_sip_docs for vendor-specific quirks of the scenario; render_sip_ladder if the user does have a real trace.. It is categorised as a Destructive tool in the SIPFlow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SIPFlow MCP server in PolicyLayer and add a rule for sip_ladder_example: 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 SIPFlow. Nothing to install.
sip_ladder_example is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sip_ladder_example 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 sip_ladder_example. 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.
sip_ladder_example is provided by the SIPFlow MCP server (sipflow/sipflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 SIPFlow 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.