assess_pqc_readiness
AI agents call assess_pqc_readiness to retrieve information from Crypto Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Post-quantum cryptography readiness assessment is fundamentally an analytical operation—it evaluates systems against PQC standards and reports findings without creating, modifying, executing, deleting, or moving resources. It belongs in the 'Read' category as a query/analysis tool. Low severity because misuse would only retrieve/expose assessment data, not trigger external operations or cause damage. Confidence is 0.
From the tool's definition Tool name 'assess_pqc_readiness' indicates assessment/analysis of post-quantum cryptography readiness. Sibling tools like 'analyze_cnsa_compliance', 'audit_crypto_usage', 'check_fips_compliance', and 'detect_cipher_type' are all inspection/analysis functions…
Attacks that exploit this kind of access
assess_pqc_readiness. It is categorised as a Read tool in the Crypto Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crypto Tools MCP Server MCP server in PolicyLayer and add a rule for assess_pqc_readiness: 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.
assess_pqc_readiness 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 assess_pqc_readiness 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 assess_pqc_readiness. 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.
assess_pqc_readiness 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →