Medium Risk

generate_rsa

[rsa] 生成 RSA 密钥对。 【参数】 - key_size:2048 / 3072 / 4096(位) - private_key_password:可选,设置后私钥 PEM 用 AES-256-CBC 加密保护 【输出】public_key_in_pem、private_key_in_pem、key_size。 【后续操作】公钥用于 rsa_encryption / rsa_verify,私钥用于 rsa_decryption / rsa_sign。

Part of the CipherHUB Cryptography Toolkit server.

generate_rsa can modify CipherHUB Cryptography Toolkit data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CIPHERHUB CRYPTOGRAPHY TOOLKIT →

Free to start. No card required.

AI agents use generate_rsa to create or modify resources in CipherHUB Cryptography Toolkit. 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 generate_rsa repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach CipherHUB Cryptography Toolkit.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_rsa": {
      "limits": [
        {
          "counter": "generate_rsa_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full CipherHUB Cryptography Toolkit policy for all 32 tools.

Get this rule live on your own CipherHUB Cryptography Toolkit server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CIPHERHUB CRYPTOGRAPHY TOOLKIT →

View all 32 tools →

These attack patterns abuse exactly the kind of access generate_rsa gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so generate_rsa only ever does what you allow.

SECURE CIPHERHUB CRYPTOGRAPHY TOOLKIT →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the generate_rsa tool do? +

[rsa] 生成 RSA 密钥对。 【参数】 - key_size:2048 / 3072 / 4096(位) - private_key_password:可选,设置后私钥 PEM 用 AES-256-CBC 加密保护 【输出】public_key_in_pem、private_key_in_pem、key_size。 【后续操作】公钥用于 rsa_encryption / rsa_verify,私钥用于 rsa_decryption / rsa_sign。. It is categorised as a Write tool in the CipherHUB Cryptography Toolkit 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_rsa? +

Register the CipherHUB Cryptography Toolkit MCP server in PolicyLayer and add a rule for generate_rsa: 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 CipherHUB Cryptography Toolkit. Nothing to install.

What risk level is generate_rsa? +

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

Can I rate-limit generate_rsa? +

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

Set action: deny in the PolicyLayer policy for generate_rsa. 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_rsa? +

generate_rsa is provided by the CipherHUB Cryptography Toolkit MCP server (https://tools.cipherhub.cloud/cipherhub/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CipherHUB Cryptography Toolkit tool call.

Deterministic rules across all 32 CipherHUB Cryptography Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.