Get one vault's details by vlt_* id (display name, metadata, timestamps).
AI agents call vault_get 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.
This tool retrieves and displays vault information (display name, metadata, timestamps) by ID. There are no side effects, data modification, deletion, execution, or financial operations. The action is purely informational and read-only, making it the lowest-risk category.
From the tool's definition Tool name 'vault_get' combined with description 'Get one vault's details by `vlt_*` id (display name, metadata, timestamps)' indicates a read-only retrieval operation that returns vault metadata without modification.
Attacks that exploit this kind of access
Get one vault's details by vlt_* id (display name, metadata, timestamps). 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_get: 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_get 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_get 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_get. 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_get 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 →