Get most recent messages, including their associated Conversation, Creator, and Labels information.
AI agents call get_recent_messages 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.
This tool performs a query operation to retrieve historical message data. It has no capability to create, modify, delete, or execute operations—only to fetch and display existing information. The blast radius of misuse is minimal, as an agent could at worst read messages it has access to, which may involve privacy concerns but no irreversible or financial damage.
From the tool's definition Tool name 'get_recent_messages' and description 'Get most recent messages, including their associated Conversation, Creator, and Labels information' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_recent_messages gives an agent:
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_recent_messages:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_messages": {}
}
} get_recent_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get most recent messages, including their associated Conversation, Creator, and Labels information. It is categorised as a Read tool in the Carbon Voice MCP Server, which means it retrieves data without modifying state.
Register the Carbon Voice MCP server in PolicyLayer and add a rule for get_recent_messages: 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.
get_recent_messages 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_recent_messages 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_recent_messages. 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_recent_messages 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.
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.