AI agents use remove_tags to create or update resources in Devon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Devon environment.
Removing tags is a reversible metadata modification — tags can be re-added. This is a Write operation (modifying existing record metadata), not Destructive since no data or records are deleted and the action can be undone by re-applying the tags.
From the tool's definition Removes tags from a specific record in DEVONthink
Attacks that exploit this kind of access
Removes tags from a specific record in DEVONthink. It is categorised as a Write tool in the Devon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Devon MCP server in PolicyLayer and add a rule for remove_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 Devon. Nothing to install.
remove_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 remove_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 remove_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.
remove_tags is provided by the Devon MCP server (mnott/devon). 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 →