generate_key · Crypto Tools MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_key does on Crypto Tools MCP Server

AI agents use generate_key to create or update resources in Crypto Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crypto Tools MCP Server environment.

WHY IT NEEDS A POLICY

Why generate_key needs a policy

Key generation creates new data (cryptographic keys) that can be used in downstream operations. This is a reversible Write action—generated keys can be discarded or replaced. Severity is medium because misuse (e.g., generating weak keys, exposing them) could compromise security posture, but the tool itself does not execute code, destroy data, or move money.

From the tool's definition Tool name 'generate_key' indicates creation of cryptographic key material. Description is empty, limiting specificity. Context from sibling tools (FIPS 140-3, CNSA 2.0, post-quantum assessment) suggests legitimate cryptographic use case.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_key Rate-limited

generate_key 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": {
    "generate_key": {
      "limits": [
        {
          "counter": "generate_key_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 Crypto Tools MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_key

What does the generate_key tool do? +

generate_key. It is categorised as a Write tool in the Crypto Tools 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_key? +

Register the Crypto Tools MCP Server MCP server in PolicyLayer and add a rule for generate_key: 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 Crypto Tools MCP Server. Nothing to install.

What risk level is generate_key? +

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

Can I rate-limit generate_key? +

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

Set action: deny in the PolicyLayer policy for generate_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_key? +

generate_key is provided by the Crypto Tools MCP Server MCP server (marc-shade/crypto-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.