[pqc_kem] 使用 ML-KEM 公钥执行密钥封装（FIPS 203）。 【算法】ML-KEM-512 / ML-KEM-768 / ML-KEM-1024。 【参数】 - algorithm：必须与 keygen 时一致 - public_key_in_hex：ml_kem_keygen 返回的公钥 hex 【输出】ciphertext_in_hex、ciphertext_in_base64、shared_secret_in_hex、shared_secret_in_base64、shared_secret_sha256、ciphertext_bytes、shared_secre...
Part of the CipherHUB Cryptography Toolkit server.
Free to start. No card required.
AI agents call ml_kem_encap to retrieve information from CipherHUB Cryptography Toolkit without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though ml_kem_encap only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"ml_kem_encap": {}
}
}See the full CipherHUB Cryptography Toolkit policy for all 32 tools.
These attack patterns abuse exactly the kind of access ml_kem_encap gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
[pqc_kem] 使用 ML-KEM 公钥执行密钥封装（FIPS 203）。 【算法】ML-KEM-512 / ML-KEM-768 / ML-KEM-1024。 【参数】 - algorithm：必须与 keygen 时一致 - public_key_in_hex：ml_kem_keygen 返回的公钥 hex 【输出】ciphertext_in_hex、ciphertext_in_base64、shared_secret_in_hex、shared_secret_in_base64、shared_secret_sha256、ciphertext_bytes、shared_secret_bytes、algorithm。 【说明】每次 encap 产生不同密文（随机化），共享密钥始终 32 字节。发送 ciphertext 给密钥持有方，对方用 ml_kem_decap 恢复相同的 shared_secret。. It is categorised as a Read tool in the CipherHUB Cryptography Toolkit MCP Server, which means it retrieves data without modifying state.
Register the CipherHUB Cryptography Toolkit MCP server in PolicyLayer and add a rule for ml_kem_encap: 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.
ml_kem_encap is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ml_kem_encap 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.
Set action: deny in the PolicyLayer policy for ml_kem_encap. 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.
ml_kem_encap 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.
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.