Stop a running capture session and analyze packets. LLMs control all analysis parameters including display filters and output formats. Can use saved configurations.
AI agents invoke stop_capture_session to trigger actions in SharkMCP. 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.
This tool triggers external operations (packet capture termination and analysis) and applies user-controlled parameters (display filters, output formats) to determine execution behavior. While not destructive (packet data is not deleted), it is clearly Execute-class because it runs a network monitoring operation whose effects are contingent on argument values.
From the tool's definition Tool can 'stop a running capture session and analyze packets' with 'LLMs control all analysis parameters including display filters and output formats.' This directly executes network packet capture and analysis operations whose side effects (what data is…
Documented attack patterns abuse exactly the kind of access stop_capture_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SharkMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_capture_session:
{
"version": "1",
"default": "deny",
"tools": {
"stop_capture_session": {
"limits": [
{
"counter": "stop_capture_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_capture_session 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.
Free to start. No card required.
Stop a running capture session and analyze packets. LLMs control all analysis parameters including display filters and output formats. Can use saved configurations. It is categorised as a Execute tool in the SharkMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shark MCP server in PolicyLayer and add a rule for stop_capture_session: 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 SharkMCP. Nothing to install.
stop_capture_session 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 stop_capture_session 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 stop_capture_session. 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.
stop_capture_session is provided by the Shark MCP server (tuliperis/sharkmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 SharkMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 SharkMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.