send_message · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What send_message does on Lichess Integration

AI agents use send_message to create or update resources in Lichess Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess Integration environment.

PARAMETERS

Parameter	Type	Required	Description
`text`	string	—	Message text
`username`	string	—	Username of the recipient

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why send_message needs a policy

This tool creates new data (a private message) that is reversible (messages can be deleted or edited by users). It has no destructive effects, does not execute arbitrary code, and does not involve financial transactions. The moderate severity reflects that message harassment or spam could degrade user experience, but the blast radius is limited to interpersonal communication within the Lichess community.

From the tool's definition Tool name 'send_message' and description 'Send a private message to another player' indicate creation of new message data in the Lichess platform's messaging system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_message Rate-limited

send_message 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_message": {
      "limits": [
        {
          "counter": "send_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lichess Integration, so you can run agents against it safely.

FAQ

Questions about send_message

What does the send_message tool do? +

Send a private message to another player. It is categorised as a Write tool in the Lichess Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does send_message accept? +

send_message accepts 2 parameters: text, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on send_message? +

Register the Lichess Integration MCP server in PolicyLayer and add a rule for send_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 Lichess Integration. Nothing to install.

What risk level is send_message? +

send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_message? +

Yes. Add a rate_limit block to the send_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.

How do I block send_message completely? +

Set action: deny in the PolicyLayer policy for send_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.

What MCP server provides send_message? +

send_message is provided by the Lichess Integration MCP server (karayaman/lichess-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.