This record as markdown: /tools/frontmcp/delete-vault-entry.md
What delete-vault-entry does on Frontmcp
AI agents call delete-vault-entry to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-vault-entry is rated Critical
The tool performs an irreversible deletion operation on sensitive authorization data stored in a vault. Once deleted, the entry cannot be recovered without restore mechanisms external to this tool. The high severity reflects the potential for an AI agent to inadvertently delete critical authentication credentials, blocking legitimate access or operations.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an authorization vault entry'. This irreversibly removes stored credentials or secrets from a vault.
Attacks that exploit this kind of access
The rule that runs delete-vault-entry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-vault-entry, this is the rule to start with:
delete-vault-entry is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every delete-vault-entry call is checked against it from then on.
Questions about delete-vault-entry
Delete an authorization vault entry. It is categorised as a Destructive tool in the Frontmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Front MCP server in PolicyLayer and add a rule for delete-vault-entry: 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 Frontmcp. Nothing to install.
delete-vault-entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-vault-entry 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 delete-vault-entry. 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.
delete-vault-entry is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue