AI agents use update-routine to create or update resources in Routine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Routine environment.
This is a Write operation because it creates or modifies data reversibly. Unlike Destructive operations (delete-routine), updates can be undone by applying further updates. However, severity is high because routines are composite tools that can chain actions from multiple MCP servers; malicious modification of a routine could cause subsequent executions to perform unintended operations, affecting downstream systems.
From the tool's definition The tool "update-routine" modifies existing routine definitions. The description states "Update a routine by name" and "update only the portion specified by the user", indicating reversible modification of stored routine data.
Attacks that exploit this kind of access
Update a routine by name. Factor in the existing schema and update only the portion specified by the user. Always confirm with user that they want to update it. User may supply a name that. It is categorised as a Write tool in the Routine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Routine MCP server in PolicyLayer and add a rule for update-routine: 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 Routine. Nothing to install.
update-routine 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-routine 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-routine. 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-routine is provided by the Routine MCP server (mquan/mcp-routine). 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 →