High Risk

deploy_private_message_contract

Deploys the PrivateMessage contract on the COTI blockchain. This contract allows sending encrypted messages to specific addresses. Only the intended recipient can decrypt a message using their own AES key. Returns the contract address and ABI needed for send_private_message and read_private_message.

Handles credentials or secrets (private_key)

Part of the COTI MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

davibauer/coti-mcp Execute Risk 4/5

AI agents invoke deploy_private_message_contract to trigger processes or run actions in COTI MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

deploy_private_message_contract can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

davibauer-coti-mcp.yaml
tools:
  deploy_private_message_contract:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full COTI MCP Server policy for all 44 tools.

Tool Name deploy_private_message_contract
Category Execute
Risk Level High

View all 44 tools →

What does the deploy_private_message_contract tool do? +

Deploys the PrivateMessage contract on the COTI blockchain. This contract allows sending encrypted messages to specific addresses. Only the intended recipient can decrypt a message using their own AES key. Returns the contract address and ABI needed for send_private_message and read_private_message.. It is categorised as a Execute tool in the COTI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_private_message_contract? +

Add a rule in your Intercept YAML policy under the tools section for deploy_private_message_contract. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the COTI MCP Server MCP server.

What risk level is deploy_private_message_contract? +

deploy_private_message_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_private_message_contract? +

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

How do I block deploy_private_message_contract completely? +

Set action: deny in the Intercept policy for deploy_private_message_contract. 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 deploy_private_message_contract? +

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

Enforce policies on COTI MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.