Low Risk

voip_calls

VoIP call list with state, duration, and participant addresses.

How to control voip_calls ↓

AI agents call voip_calls to retrieve information from SharkMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool reads and extracts call metadata from already-captured packet data. It performs no write, execute, or destructive operations. The data returned is informational only and derived from passive packet inspection. Severity is low because misuse results only in information disclosure from captured traffic, not code execution, data modification, or financial impact.

From the tool's definition Tool name 'voip_calls' and description indicate it retrieves and lists VoIP call metadata (state, duration, participant addresses) from PCAP analysis. No modification, deletion, or execution capability is described.

Documented attack patterns abuse exactly the kind of access voip_calls 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 voip_calls:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "voip_calls": {}
  }
}

voip_calls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SharkMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the voip_calls tool do? +

VoIP call list with state, duration, and participant addresses. It is categorised as a Read tool in the SharkMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on voip_calls? +

Register the Shark MCP server in PolicyLayer and add a rule for voip_calls: 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.

What risk level is voip_calls? +

voip_calls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit voip_calls? +

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

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

voip_calls is provided by the Shark MCP server (weirdmachine64/sharkmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SharkMCP tool call.

Deterministic rules across all 30 SharkMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 SharkMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.