Post a message to the shared team channel. Agents on wait_for_message wake instantly.
AI agents use post_message to create or update resources in Claude Team MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Team MCP environment.
The tool creates new message data in a shared communication channel. This is a Write-category action because: (1) it modifies state by adding a message, (2) the effect is reversible (messages can be deleted or overwritten), and (3) it has no destructive, financial, or arbitrary code execution capability.
From the tool's definition Tool description states 'Post a message to the shared team channel.' This is a write operation that creates new data (messages) in a reversible manner. Messages can be read, deleted, or edited without permanent destruction.
Attacks that exploit this kind of access
Post a message to the shared team channel. Agents on wait_for_message wake instantly. It is categorised as a Write tool in the Claude Team MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Team 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 Team MCP. 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 Team MCP server (lakshan12367/mcp). 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 →