secret-engines-list
AI agents call secret-engines-list 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.
This tool retrieves information about secret engines in Vault without modifying, deleting, or executing operations. Listing secret engines is a query operation with no side effects. While knowledge of available secret engines could inform an attacker, the tool itself performs no state changes and presents minimal risk.
From the tool's definition Tool name 'secret-engines-list' indicates a listing/enumeration operation. The server description states it 'provides tools for system backend administration' and the sibling tools show patterns of read operations (-list, -read, -enable, -disable).
Attacks that exploit this kind of access
secret-engines-list. 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 secret-engines-list: 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.
secret-engines-list 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 secret-engines-list 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 secret-engines-list. 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.
secret-engines-list 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 →