pushtodisplay_send_update · Pushtodisplay MCP: Risk & Policy

WHAT IT DOES

What pushtodisplay_send_update does on Pushtodisplay

AI agents use pushtodisplay_send_update 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.

WHY IT NEEDS A POLICY

Why pushtodisplay_send_update needs a policy

The tool publishes/sends content to connected devices, which is a write/broadcast operation. It creates new display state on remote devices but does not irreversibly delete data or involve financial transactions. Misuse could push unwanted content to all connected iOS/Android devices on a board, hence medium severity.

From the tool's definition Send a display update to a PushToDisplay board. Publishes text content to all devices connected to the specified board.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pushtodisplay_send_update Rate-limited

pushtodisplay_send_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pushtodisplay_send_update": {
      "limits": [
        {
          "counter": "pushtodisplay_send_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pushtodisplay, so you can run agents against it safely.

FAQ

Questions about pushtodisplay_send_update

What does the pushtodisplay_send_update tool do? +

Send a display update to a PushToDisplay board. Publishes text content to all devices connected to the specified 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.

How do I enforce a policy on pushtodisplay_send_update? +

Register the Pushtodisplay MCP server in PolicyLayer and add a rule for pushtodisplay_send_update: 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.

What risk level is pushtodisplay_send_update? +

pushtodisplay_send_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pushtodisplay_send_update? +

Yes. Add a rate_limit block to the pushtodisplay_send_update 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.

How do I block pushtodisplay_send_update completely? +

Set action: deny in the PolicyLayer policy for pushtodisplay_send_update. 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.

What MCP server provides pushtodisplay_send_update? +

pushtodisplay_send_update 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.