pqc_encapsulate · Post-Quantum Cryptography MCP Server MCP

WHAT IT DOES

What pqc_encapsulate does on Post-Quantum Cryptography MCP Server

AI agents invoke pqc_encapsulate to trigger actions in Post-Quantum Cryptography MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why pqc_encapsulate needs a policy

This tool performs a cryptographic key encapsulation operation — it runs a KEM algorithm to generate and wrap a shared secret using a public key. This is an active cryptographic execution (producing ciphertext and a shared secret), not merely reading data or writing stored data.

From the tool's definition Encapsulate a shared secret using a KEM public key (key encapsulation)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pqc_encapsulate Rate-limited

pqc_encapsulate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pqc_encapsulate": {
      "limits": [
        {
          "counter": "pqc_encapsulate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Post-Quantum Cryptography MCP Server, so you can run agents against it safely.

FAQ

Questions about pqc_encapsulate

What does the pqc_encapsulate tool do? +

Encapsulate a shared secret using a KEM public key (key encapsulation). It is categorised as a Execute tool in the Post-Quantum Cryptography MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pqc_encapsulate? +

Register the Post-Quantum Cryptography MCP Server MCP server in PolicyLayer and add a rule for pqc_encapsulate: 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 Post-Quantum Cryptography MCP Server. Nothing to install.

What risk level is pqc_encapsulate? +

pqc_encapsulate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pqc_encapsulate? +

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

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

pqc_encapsulate is provided by the Post-Quantum Cryptography MCP Server MCP server (scottdhughes/post-quantum-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.