create_self_signed_certificate

WHAT IT DOES

What create_self_signed_certificate does on PKI Studio MCP

AI agents use create_self_signed_certificate to create or update resources in PKI Studio MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PKI Studio MCP environment.

WHY IT NEEDS A POLICY

Why create_self_signed_certificate needs a policy

This tool creates (generates) a new X.509 certificate artifact, which is a reversible action—certificates can be discarded or regenerated. While certificate creation is a legitimate PKI operation, misuse by an AI agent could result in unauthorized or fraudulent certificates being generated if provided with compromised key material or spoofed identity information.

From the tool's definition Tool creates a self-signed X.509 certificate from supplied cryptographic key material and subject DN. The verb 'create' and the action of generating a new certificate artifact indicate data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_self_signed_certificate Rate-limited

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

FAQ

Questions about create_self_signed_certificate

What does the create_self_signed_certificate tool do? +

Create a self-signed X.509 certificate from a PKCS#8 private key, SPKI public key, and subject DN. It is categorised as a Write tool in the PKI Studio MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_self_signed_certificate? +

Register the PKI Studio MCP server in PolicyLayer and add a rule for create_self_signed_certificate: 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 create_self_signed_certificate? +

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

Can I rate-limit create_self_signed_certificate? +

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

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

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