pqc_key_store_save | PolicyLayer

WHAT IT DOES

What pqc_key_store_save does on Post-Quantum Cryptography MCP Server

AI agents use pqc_key_store_save to create or update resources in Post-Quantum Cryptography MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Post-Quantum Cryptography MCP Server environment.

WHY IT NEEDS A POLICY

Why pqc_key_store_save needs a policy

This tool saves/stores cryptographic key material in session-scoped memory. While the data is not persisted to disk, it modifies the in-memory state by creating a named reference to key material. This is a Write operation rather than Read (non-destructive modification).

From the tool's definition Tool description states 'Save a keygen output by name' indicating it creates or modifies data (storing cryptographic keys in session memory). The name contains 'save' which is a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pqc_key_store_save Rate-limited

pqc_key_store_save stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_key_store_save": {
      "limits": [
        {
          "counter": "pqc_key_store_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_key_store_save

What does the pqc_key_store_save tool do? +

Save a keygen output by name for convenient reference. Session-scoped, no persistence. It is categorised as a Write tool in the Post-Quantum Cryptography MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pqc_key_store_save? +

Register the Post-Quantum Cryptography MCP Server MCP server in PolicyLayer and add a rule for pqc_key_store_save: 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_key_store_save? +

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

Can I rate-limit pqc_key_store_save? +

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

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

pqc_key_store_save 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.