Update an existing message
AI agents use update_message to create or update resources in Follow Plan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Follow Plan MCP Server environment.
This tool creates or modifies data reversibly by updating message content. It does not delete data (which would be Destructive) nor does it execute arbitrary code or trigger external operations (which would be Execute). The blast radius is medium because message modifications could affect communication history and project documentation, but changes are reversible via further updates or backups.
From the tool's definition Tool name is 'update_message' and description states 'Update an existing message'. This modifies existing data (the message content) in a reversible manner.
Attacks that exploit this kind of access
Update an existing message. It is categorised as a Write tool in the Follow Plan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Follow Plan MCP Server MCP server in PolicyLayer and add a rule for update_message: 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 Follow Plan MCP Server. Nothing to install.
update_message 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_message 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_message. 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_message is provided by the Follow Plan MCP Server MCP server (vibeclasses/follow-plan-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 →