AI agents use update_node to create or update resources in Pen — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pen environment.
The tool modifies existing data (node properties) in a reversible manner. This is a classic Write operation—it creates or updates data without permanently destroying it. The shallow-merge behavior confirms that updates are partial and non-destructive.
From the tool's definition Tool description states it 'Update[s] properties of an existing node' and 'shallow-merged', indicating reversible modification of data without deletion or destruction.
Attacks that exploit this kind of access
Update properties of an existing node. Only provided properties are shallow-merged; unmentioned properties remain unchanged. Returns the updated node state. It is categorised as a Write tool in the Pen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pen MCP server in PolicyLayer and add a rule for update_node: 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 Pen. Nothing to install.
update_node 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_node 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_node. 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_node is provided by the Pen MCP server (@zseven-w/pen-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 →