identity-oidc-key-read
AI agents call identity-oidc-key-read to retrieve information from Vault MCP Server (mschuchard) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or query OIDC key identity information from Vault's identity subsystem based on its name. This is a Read operation (retrieves data without side effects). However, the empty description creates moderate uncertainty.
From the tool's definition Tool name contains 'read' and is part of Vault's identity OIDC key management system. Description is empty, limiting definitive assessment.
Attacks that exploit this kind of access
identity-oidc-key-read. It is categorised as a Read tool in the Vault MCP Server (mschuchard) MCP Server, which means it retrieves data without modifying state.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for identity-oidc-key-read: 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 Vault MCP Server (mschuchard). Nothing to install.
identity-oidc-key-read is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the identity-oidc-key-read 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.
Set action: deny in the PolicyLayer policy for identity-oidc-key-read. 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.
identity-oidc-key-read is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →