raft-config-read
AI agents call raft-config-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.
This tool retrieves Vault's Raft cluster configuration without modifying it. However, Raft configuration details (node identities, cluster state, leadership info) are sensitive operational data that could inform attacks on Vault's availability or cluster integrity. Severity is medium rather than low due to the critical nature of Vault infrastructure, even though the read itself is non-destructive.
From the tool's definition Tool name 'raft-config-read' explicitly indicates a read operation on Vault's Raft consensus configuration. The 'read' suffix and lack of write/delete keywords confirm read-only intent.
Attacks that exploit this kind of access
raft-config-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 raft-config-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.
raft-config-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 raft-config-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 raft-config-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.
raft-config-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 →