[sm2] SM2 公钥验签。 【参数】 - sm2_public_key_in_pem：PEM 格式公钥 - data_in_hex：待验签数据 Hex。 · RAW 模式（sign_raw_data_mode=True）：消息原文 Hex，服务端走标准 SM2 流程，内部计算 e = SM3(ZA || M) 后验签。 · DIGEST 模式（sign_raw_data_mode=False）：必须传 32 字节 SM3 摘要 e 的 Hex（64 个 hex 字符），服务端不再做任何隐式 SM3，直接对 e 做裸 SM2 验签，与 KMS / ECC / RSA 的 DIGEST ...
Part of the CipherHUB Cryptography Toolkit server.
Free to start. No card required.
AI agents call sm2_verify 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 sm2_verify 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": {
"sm2_verify": {}
}
}See the full CipherHUB Cryptography Toolkit policy for all 32 tools.
These attack patterns abuse exactly the kind of access sm2_verify 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.
[sm2] SM2 公钥验签。 【参数】 - sm2_public_key_in_pem：PEM 格式公钥 - data_in_hex：待验签数据 Hex。 · RAW 模式（sign_raw_data_mode=True）：消息原文 Hex，服务端走标准 SM2 流程，内部计算 e = SM3(ZA || M) 后验签。 · DIGEST 模式（sign_raw_data_mode=False）：必须传 32 字节 SM3 摘要 e 的 Hex（64 个 hex 字符），服务端不再做任何隐式 SM3，直接对 e 做裸 SM2 验签，与 KMS / ECC / RSA 的 DIGEST 模式语义一致。 - signature_in_hex：签名 Hex（必须为 RS_ASN1 格式） - signature_format：固定为 RS_ASN1 - sign_raw_data_mode：必须与签名时一致；True=RAW，False=DIGEST 【输出】verified（bool，True=验签通过）。 【完整流程】generate_sm2 → sm2_sign → sm2_verify. 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 sm2_verify: 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.
sm2_verify 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 sm2_verify 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 sm2_verify. 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.
sm2_verify 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.