Medium Risk

account.create_api_key

Create a new API key for headless MCP authentication. The key will be shown ONCE - make sure to save it securely. Use the key with: claude mcp add --transport http autodock https://autodock.io/api/mcp/streamable-http --header "Authorization: Bearer <key>"

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

mikesol/autodock Write Risk 2/5

AI agents use account.create_api_key to create or modify resources in Autodock. 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 account.create_api_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 Autodock.

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

mikesol-autodock.yaml
tools:
  account.create_api_key:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Autodock policy for all 27 tools.

Tool Name account.create_api_key
Category Write
MCP Server Autodock MCP Server
Risk Level Medium

View all 27 tools →

Agents calling write-class tools like account.create_api_key have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the account.create_api_key tool do? +

Create a new API key for headless MCP authentication. The key will be shown ONCE - make sure to save it securely. Use the key with: claude mcp add --transport http autodock https://autodock.io/api/mcp/streamable-http --header "Authorization: Bearer <key>". It is categorised as a Write tool in the Autodock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on account.create_api_key? +

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

What risk level is account.create_api_key? +

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

Can I rate-limit account.create_api_key? +

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

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

account.create_api_key is provided by the Autodock MCP server (mikesol/autodock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Autodock

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.