Send an encrypted message to a specific recipient address on a deployed PrivateMessage contract. The message is encrypted using COTI MPC so only the recipient can decrypt it with their own AES key. Requires the contract address and ABI returned by deploy_private_message_contract.
Handles credentials or secrets (private_key); Single-target operation
Part of the COTI MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use send_private_message to create or modify resources in COTI MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call send_private_message repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach COTI MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
send_private_message:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full COTI MCP Server policy for all 44 tools.
Send an encrypted message to a specific recipient address on a deployed PrivateMessage contract. The message is encrypted using COTI MPC so only the recipient can decrypt it with their own AES key. Requires the contract address and ABI returned by deploy_private_message_contract.. It is categorised as a Write tool in the COTI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for send_private_message. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the COTI MCP Server MCP server.
send_private_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 send_private_message rule in your Intercept 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 Intercept policy for send_private_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.
send_private_message is provided by the COTI MCP Server MCP server (davibauer/coti-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept