Replace the tags on a page. Tags must already exist in the Collective; pass tag ids (use list_tags to look them up).
AI agents use set_page_tags to create or update resources in Collectives — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Collectives environment.
This tool modifies page attributes (tags) but does not delete, destroy, or execute arbitrary operations. The change is reversible—tags can be replaced again with different values. While it does alter data, the scope is limited to tag associations on a page, making it a Write operation.
From the tool's definition Tool description states 'Replace the tags on a page', which modifies page metadata. The term 'Replace' indicates reversible alteration of existing tags, not deletion of the page itself. Tag assignment is a standard write operation.
Attacks that exploit this kind of access
Replace the tags on a page. Tags must already exist in the Collective; pass tag ids (use list_tags to look them up). It is categorised as a Write tool in the Collectives MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Collectives MCP server in PolicyLayer and add a rule for set_page_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 Collectives. Nothing to install.
set_page_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 set_page_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 set_page_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.
set_page_tags is provided by the Collectives MCP server (megamaced/nc_collectives-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 →