MCP Tool Reference Low Risk

read_pki_issuer

Read details about a specific PKI issuer

Part of the HashiCorp Vault MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

WHEN AI AGENTS USE THIS TOOL

AI agents call read_pki_issuer to retrieve information from HashiCorp Vault without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.

WHY ENFORCE A POLICY ON READ_PKI_ISSUER

Even though read_pki_issuer only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

hashicorp-vault.yaml
tools:
  read_pki_issuer:
    rules:
      - action: allow

See the full HashiCorp Vault policy for all 20 tools.

DETAILS

Tool Name

read_pki_issuer

Category

Read

Risk Level

Low

MORE HASHICORP VAULT TOOLS

View all 20 tools →

SIMILAR READ TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the read_pki_issuer tool do?

Read details about a specific PKI issuer. It is categorised as a Read tool in the HashiCorp Vault MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_pki_issuer?

Add a rule in your Intercept YAML policy under the tools section for read_pki_issuer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the HashiCorp Vault MCP server.

What risk level is read_pki_issuer?

read_pki_issuer is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_pki_issuer?

Yes. Add a rate_limit block to the read_pki_issuer rule in your Intercept 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 read_pki_issuer completely?

Set action: deny in the Intercept policy for read_pki_issuer. 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 read_pki_issuer?

read_pki_issuer is provided by the HashiCorp Vault MCP server (hashicorp/vault-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON HASHICORP VAULT

Open source. One binary. Zero dependencies.