kya_generate_keypair · Agent Safety MCP: Risk & Policy

WHAT IT DOES

What kya_generate_keypair does on Agent Safety

AI agents invoke kya_generate_keypair to trigger actions in Agent Safety. 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 kya_generate_keypair needs a policy

This tool executes a cryptographic operation (key pair generation) that produces new cryptographic material. It is not a simple read (it creates new keys), not a write to an external data store per se, but it executes a cryptographic process with outputs that could be used to forge or impersonate agent identities if misused.

From the tool's definition Generate an Ed25519 keypair for signing agent identity cards

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kya_generate_keypair Rate-limited

kya_generate_keypair 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": {
    "kya_generate_keypair": {
      "limits": [
        {
          "counter": "kya_generate_keypair_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 Agent Safety, so you can run agents against it safely.

FAQ

Questions about kya_generate_keypair

What does the kya_generate_keypair tool do? +

Generate an Ed25519 keypair for signing agent identity cards. It is categorised as a Execute tool in the Agent Safety MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kya_generate_keypair? +

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

What risk level is kya_generate_keypair? +

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

Can I rate-limit kya_generate_keypair? +

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

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

kya_generate_keypair is provided by the Agent Safety MCP server (luciferforge/agent-safety-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.