Post a message into a target inbox (channel).
AI agents use post_message to create or update resources in Claude ↔ Codex MCP Relay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude ↔ Codex MCP Relay environment.
This tool creates/writes data (messages) reversibly. Messages can typically be edited or deleted, so it's not destructive. It doesn't execute code, access financial systems, or retrieve data. The medium severity reflects that misuse could spam channels, post misleading information, or disrupt collaborative workflows, but the impact is limited to message data which remains recoverable.
From the tool's definition Tool description states 'Post a message into a target inbox (channel)' — this creates new message data in a channel.
Attacks that exploit this kind of access
Post a message into a target inbox (channel). It is categorised as a Write tool in the Claude ↔ Codex MCP Relay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude ↔ Codex MCP Relay MCP server in PolicyLayer and add a rule for post_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 Claude ↔ Codex MCP Relay. Nothing to install.
post_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the post_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.
Set action: deny in the PolicyLayer policy for post_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.
post_message is provided by the Claude ↔ Codex MCP Relay MCP server (wiresharks/claudecodex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →