Removes specific tags from a document, leaving other tags intact
AI agents use remove_tags_from_document to create or update resources in RSpace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSpace MCP Server environment.
This tool modifies document metadata by removing specific tags, but leaves other tags intact and does not delete the document itself. This is a reversible modification (tags can be re-added), placing it in the Write category. Misuse could cause loss of metadata organization but is not irreversible.
From the tool's definition 'Removes specific tags from a document, leaving other tags intact'
Attacks that exploit this kind of access
Removes specific tags from a document, leaving other tags intact. It is categorised as a Write tool in the RSpace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for remove_tags_from_document: 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 RSpace MCP Server. Nothing to install.
remove_tags_from_document 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_from_document 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_from_document. 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_from_document is provided by the RSpace MCP Server MCP server (rspace-os/rspace-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 →