Update an existing board
AI agents use pushtodisplay_update_board to create or update resources in Pushtodisplay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pushtodisplay environment.
This tool modifies an existing board's configuration or content, which is a reversible write operation. It does not delete data (which would be Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions (Financial). The 'medium' severity reflects that an agent could modify board content or settings affecting multiple devices, but changes are reversible via another update.
From the tool's definition Tool name contains 'update' and description states 'Update an existing board'. Update operations modify data reversibly without deletion.
Attacks that exploit this kind of access
Update an existing board. It is categorised as a Write tool in the Pushtodisplay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pushtodisplay MCP server in PolicyLayer and add a rule for pushtodisplay_update_board: 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 Pushtodisplay. Nothing to install.
pushtodisplay_update_board 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 pushtodisplay_update_board 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 pushtodisplay_update_board. 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.
pushtodisplay_update_board is provided by the Pushtodisplay MCP server (pushtodisplay/cli). 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 →