Update the tags on a secret without touching its value.
AI agents use vault_update_tags to create or update resources in Secret Vault MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Secret Vault MCP Server environment.
This tool modifies secret metadata (tags) rather than the secret value itself or deleting data, placing it in the Write category. Severity is medium because an attacker could alter tags to misdirect secret usage or corrupt metadata organization, but this does not expose the secret value, permanently delete it, or cause financial harm.
From the tool's definition 'Update the tags on a secret' indicates modification of metadata associated with stored secrets. Tags are mutable attributes that can be changed reversibly.
Attacks that exploit this kind of access
Update the tags on a secret without touching its value. It is categorised as a Write tool in the Secret Vault MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Secret Vault MCP Server MCP server in PolicyLayer and add a rule for vault_update_tags: 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 Secret Vault MCP Server. Nothing to install.
vault_update_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vault_update_tags 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_update_tags. 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_update_tags is provided by the Secret Vault MCP Server MCP server (sam-ueckert/vault-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 →