update_tag
AI agents use update_tag to create or update resources in Super Productivity MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Super Productivity MCP environment.
This tool modifies existing tag data, which is a reversible Write operation. Without a description, confidence is reduced slightly. The medium severity reflects that tag updates could affect task organization and filtering, but the impact is limited to metadata rather than core task data or destructive operations. The blast radius is contained within the productivity management system.
From the tool's definition Tool name 'update_tag' indicates modification of existing data. Server context shows task/project management capabilities, and update operations typically modify reversible data structures (tag properties, metadata, etc.).
Attacks that exploit this kind of access
update_tag. It is categorised as a Write tool in the Super Productivity MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Super Productivity MCP server in PolicyLayer and add a rule for update_tag: 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 Super Productivity MCP. Nothing to install.
update_tag 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 update_tag 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 update_tag. 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.
update_tag is provided by the Super Productivity MCP server (rochadelon/super-productivity-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 →