Low Risk

get_conversation

Get a conversation by its ID.

How to control get_conversation ↓

What get_conversation does on Carbon Voice

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

Low Risk

Why get_conversation needs a policy

This tool retrieves conversation data by querying with an ID parameter. It performs a simple data retrieval with no capacity to modify, delete, or execute operations. The blast radius of misuse is limited to potential unauthorized access to conversation contents, which is a read confidentiality issue rather than a destructive or operational risk. Classified as Read with low severity.

From the tool's definition Tool description states 'Get a conversation by its ID' - a retrieval operation with no modification or side effects. The verb 'Get' and the lack of any write, delete, or execute semantics clearly indicate a read-only action.

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

How to control get_conversation

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

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

get_conversation 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 Carbon Voice — 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_conversation

What does the get_conversation tool do? +

Get a conversation by its ID. It is categorised as a Read tool in the Carbon Voice MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_conversation? +

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

What risk level is get_conversation? +

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

Can I rate-limit get_conversation? +

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

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

get_conversation is provided by the Carbon Voice MCP server (phononx/cv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Carbon Voice tool call.

Start from Carbon Voice, 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.

28 Carbon Voice 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.