AI agents use send-chat to create or update resources in Defcon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defcon environment.
The send-chat tool creates new data (chat messages) that persist in the game state and are visible to other players. This is a reversible write operation—messages can be deleted or ignored, and they have no destructive consequences. While chat could theoretically be misused to spread misinformation or harassment within the game, the blast radius is limited to social/reputational impact within a single game session.
From the tool's definition Tool description states it 'Sends a chat message visible to all players in the game'. This is a write operation that creates a new message/communication artifact.
Attacks that exploit this kind of access
Sends a chat message visible to all players in the game. It is categorised as a Write tool in the Defcon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Defcon MCP server in PolicyLayer and add a rule for send-chat: 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 Defcon. Nothing to install.
send-chat 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 send-chat 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 send-chat. 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.
send-chat is provided by the Defcon MCP server (jorisvddonk/defcon-mcp-server). 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 →