Low Risk

get_message

Get a message by its ID.

How to control get_message ↓

What get_message does on Carbon Voice

AI agents call get_message 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_message needs a policy

This tool retrieves an existing message by identifier, performing a read-only query operation with no side effects, data modification, or system state changes. The low severity reflects minimal blast radius—an AI agent misusing this would only be able to access messages it queries, not create, modify, or delete data.

From the tool's definition Tool name 'get_message' and description 'Get a message by its ID' indicate data retrieval without modification. The server description confirms it includes 'retrieving messages, conversations, voice memos' as a core capability.

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

How to control get_message

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_message:

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

get_message 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_message

What does the get_message tool do? +

Get a message 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_message? +

Register the Carbon Voice MCP server in PolicyLayer and add a rule for get_message: 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_message? +

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

Can I rate-limit get_message? +

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

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

get_message 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.