Check for new incoming messages. Also happens automatically on every other tool call.
AI agents call check_inbox to retrieve information from CC2CC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of incoming messages from other agents. It has no destructive, financial, or code execution capabilities. The automatic triggering on other tool calls is a passive synchronization mechanism and does not change the classification. Severity is low because exposure to this tool allows only information retrieval about inter-agent communication, with minimal blast radius if misused.
From the tool's definition Tool description states 'Check for new incoming messages' — a retrieval operation with no side effects. It queries message state without modification.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access check_inbox gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CC2CC, and nothing reaches the server without passing your rules. This is the rule we recommend for check_inbox:
{
"version": "1",
"default": "deny",
"tools": {
"check_inbox": {}
}
}check_inbox 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.
Check for new incoming messages. Also happens automatically on every other tool call. It is categorised as a Read tool in the CC2CC MCP Server, which means it retrieves data without modifying state.
Register the CC2CC MCP server in PolicyLayer and add a rule for check_inbox: 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 CC2CC. Nothing to install.
check_inbox 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 check_inbox 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 check_inbox. 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.
check_inbox is provided by the CC2CC MCP server (non4me/cc2cc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CC2CC, 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 CC2CC tools catalogued and risk-classified — across an index of 43,000+ MCP servers.