verify_key_pair · PKI Studio MCP: Risk & Policy

WHAT IT DOES

What verify_key_pair does on PKI Studio MCP

AI agents invoke verify_key_pair to trigger actions in PKI Studio MCP. 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 verify_key_pair needs a policy

This tool executes cryptographic operations (signing and verifying) using private and public key material. It is not a pure read/query — it actively performs operations that involve use of sensitive private key material. It doesn't write or destroy data, but it does execute operations with potential security implications if misused (e.g., exposing key usage patterns or mishandling private keys).

From the tool's definition 'by signing and verifying sample data' — the tool actively performs cryptographic signing and verification operations on data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_key_pair Rate-limited

verify_key_pair 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": {
    "verify_key_pair": {
      "limits": [
        {
          "counter": "verify_key_pair_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 PKI Studio MCP, so you can run agents against it safely.

FAQ

Questions about verify_key_pair

What does the verify_key_pair tool do? +

Verify that a PKCS#8 private key matches an SPKI public key by signing and verifying sample data. It is categorised as a Execute tool in the PKI Studio MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_key_pair? +

Register the PKI Studio MCP server in PolicyLayer and add a rule for verify_key_pair: 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 PKI Studio MCP. Nothing to install.

What risk level is verify_key_pair? +

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

Can I rate-limit verify_key_pair? +

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

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

verify_key_pair is provided by the PKI Studio MCP server (pkistudio/pkistudiomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.