run_sipp_scenario · Sipp MCP: Risk & Policy

WHAT IT DOES

What run_sipp_scenario does on Sipp

AI agents invoke run_sipp_scenario to trigger actions in Sipp. 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.

WHY IT NEEDS A POLICY

Why run_sipp_scenario needs a policy

This tool invokes external network operations and protocol testing commands through SIPp. While the effects are somewhat constrained to SIP protocol testing (not arbitrary code execution), it still triggers real network activity, SIP call flows, and protocol interactions that could impact systems under test, consume resources, or be exploited to probe/attack SIP infrastructure.

From the tool's definition The tool description states it can "Execute a SIPp scenario" and "run as UAC (client) or UAS (server)". SIPp is a SIP protocol testing tool that simulates network traffic and protocol interactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_sipp_scenario Rate-limited

run_sipp_scenario stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_sipp_scenario": {
      "limits": [
        {
          "counter": "run_sipp_scenario_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sipp, so you can run agents against it safely.

FAQ

Questions about run_sipp_scenario

What does the run_sipp_scenario tool do? +

Execute a SIPp scenario for SIP protocol testing. Can run as UAC (client) or UAS (server) with custom scenarios. It is categorised as a Execute tool in the Sipp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_sipp_scenario? +

Register the Sipp MCP server in PolicyLayer and add a rule for run_sipp_scenario: 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 Sipp. Nothing to install.

What risk level is run_sipp_scenario? +

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

Can I rate-limit run_sipp_scenario? +

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

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

run_sipp_scenario is provided by the Sipp MCP server (randybritsch/sipp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.