Get details of a specific campaign.
AI agents call get_campaign to retrieve information from VoIPbin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves campaign metadata without creating, modifying, or deleting any data. It is a straightforward query operation that does not alter state or trigger external side effects beyond reading. The low severity reflects minimal risk if misused by an AI agent, as retrieval alone cannot harm system integrity or financial transactions.
From the tool's definition Tool name is 'get_campaign' and description states 'Get details of a specific campaign' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific campaign. It is categorised as a Read tool in the VoIPbin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VoIPbin MCP Server MCP server in PolicyLayer and add a rule for get_campaign: 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 VoIPbin MCP Server. Nothing to install.
get_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_campaign 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 get_campaign. 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.
get_campaign is provided by the VoIPbin MCP Server MCP server (voipbin/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_campaign is one line of VoIPbin MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →