AI agents use sendChat to create or update resources in MCP Minecraft Remote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Minecraft Remote environment.
Sending a chat message creates new data (a message) in the Minecraft server's chat log, which is a Write operation. The effect is reversible—messages can be superseded or ignored. It poses minimal risk as chat is a standard communication mechanism with no direct impact on game state, inventory, or player safety beyond potential griefing through disruptive messages.
From the tool's definition Tool name 'sendChat' and description 'Send a chat message to the Minecraft server' indicate creation of a message artifact that is reversible (can be deleted or overwritten by subsequent messages).
Documented attack patterns abuse exactly the kind of access sendChat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Minecraft Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for sendChat:
{
"version": "1",
"default": "deny",
"tools": {
"sendChat": {
"limits": [
{
"counter": "sendchat_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sendChat stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a chat message to the Minecraft server. It is categorised as a Write tool in the MCP Minecraft Remote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Minecraft Remote MCP server in PolicyLayer and add a rule for sendChat: 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 MCP Minecraft Remote. Nothing to install.
sendChat 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 sendChat 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 sendChat. 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.
sendChat is provided by the MCP Minecraft Remote MCP server (nacal/mcp-minecraft-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Minecraft Remote, 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.
27 MCP Minecraft Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.