generate_aes_key

Generate or recover an AES key for a COTI account. Requires the account to be funded. The AI assistant should track the returned AES key for use in private transactions.

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 Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use generate_aes_key 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.

// WHY ENFORCE A POLICY ON GENERATE_AES_KEY

Without a policy, an AI agent could call generate_aes_key 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.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

davibauer-coti-mcp.yaml

tools:
  generate_aes_key:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

// DETAILS

Tool Name generate_aes_key

Category Write

MCP Server COTI MCP Server MCP Server

Risk Level Medium

// MORE COTI MCP SERVER TOOLS

Financial transfer_native Financial transfer_private_erc20 Financial transfer_private_erc721 Execute compile_and_deploy_contract Execute compile_contract Execute deploy_private_erc20_contract Execute deploy_private_erc721_contract Execute deploy_private_message_contract

View all 44 tools →

// RELATED READING

// FAQ

What does the generate_aes_key tool do? +

Generate or recover an AES key for a COTI account. Requires the account to be funded. The AI assistant should track the returned AES key for use in private transactions.. 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.

How do I enforce a policy on generate_aes_key? +

Add a rule in your Intercept YAML policy under the tools section for generate_aes_key. 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 generate_aes_key? +

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

Can I rate-limit generate_aes_key? +

Yes. Add a rate_limit block to the generate_aes_key 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 generate_aes_key completely? +

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

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

generate_aes_key

Enforce policies on COTI MCP Server