vault_list
AI agents call vault_list to retrieve information from Managed Agent Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention 'vault_list' indicates the tool queries or enumerates vault contents without modifying data. The suffix '_list' is consistently a read operation across the sibling tools (agent_list, environment_list, memory_store_list). However, empty description and the sensitive nature of 'vault' operations create moderate uncertainty.
From the tool's definition Tool name 'vault_list' suggests a retrieval/enumeration operation; 'list' is a read-only verb. Description is empty, making classification uncertain.
Attacks that exploit this kind of access
vault_list. It is categorised as a Read tool in the Managed Agent Control MCP Server, which means it retrieves data without modifying state.
Register the Managed Agent Control MCP server in PolicyLayer and add a rule for vault_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 Managed Agent Control. Nothing to install.
vault_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 vault_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 vault_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.
vault_list is provided by the Managed Agent Control MCP server (modus-agendi/managed-agent-control-mcp). 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 →