Add and/or remove tags from an entity in a single call. More efficient than separate add/remove calls.
AI agents use modify_tags to create or update resources in DMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DMCP environment.
The tool creates or modifies data (tags on entities) in a reversible manner. Tags can be added or removed, and such changes are undoable through subsequent calls. This is characteristic of Write operations. It does not execute arbitrary code, delete data irreversibly, or move financial resources, so Write is the appropriate category rather than Execute, Destructive, or Financial.
From the tool's definition Tool description states 'Add and/or remove tags from an entity in a single call', which modifies entity metadata.
Documented attack patterns abuse exactly the kind of access modify_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for modify_tags:
{
"version": "1",
"default": "deny",
"tools": {
"modify_tags": {
"limits": [
{
"counter": "modify_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_tags stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add and/or remove tags from an entity in a single call. More efficient than separate add/remove calls. It is categorised as a Write tool in the DMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D MCP server in PolicyLayer and add a rule for modify_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 DMCP. Nothing to install.
modify_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 modify_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 modify_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.
modify_tags is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.