Low Risk

get_call

Retrieve call details

How to control get_call ↓

What get_call does on Voyp MCP Server

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

Low Risk

Why get_call needs a policy

This tool retrieves information about an existing call without modifying, deleting, or executing any actions. Retrieving call metadata (duration, participants, status, etc.) is a read-only operation that poses minimal risk even if misused by an AI agent, as it merely exposes information rather than enabling destructive or financial actions.

From the tool's definition Tool name is 'get_call' and description is 'Retrieve call details' — this is purely a data retrieval operation with no side effects or state modification.

Documented attack patterns abuse exactly the kind of access get_call gives an agent:

How to control get_call

PolicyLayer is an MCP gateway — it sits between your AI agents and Voyp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_call:

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

get_call 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 Voyp MCP Server — 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.

Related tools and policies

Go deeper

Questions about get_call

What does the get_call tool do? +

Retrieve call details. It is categorised as a Read tool in the Voyp MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_call? +

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

What risk level is get_call? +

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

Can I rate-limit get_call? +

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

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

get_call is provided by the Voyp MCP Server MCP server (paulotaylor/voyp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Voyp MCP Server tool call.

Start from Voyp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 Voyp MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.