Medium Risk

update_display_name

Update your display name

Part of the Poll server.

update_display_name can modify Poll data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE POLL →

Free to start. No card required.

AI agents use update_display_name to create or modify resources in Poll. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update_display_name repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Poll.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_display_name": {
      "limits": [
        {
          "counter": "update_display_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Poll policy for all 28 tools.

Get this rule live on your own Poll server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY POLL →

View all 28 tools →

These attack patterns abuse exactly the kind of access update_display_name gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so update_display_name only ever does what you allow.

SECURE POLL →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the update_display_name tool do? +

Update your display name. It is categorised as a Write tool in the Poll MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_display_name? +

Register the Poll MCP server in PolicyLayer and add a rule for update_display_name: 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 Poll. Nothing to install.

What risk level is update_display_name? +

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

Can I rate-limit update_display_name? +

Yes. Add a rate_limit block to the update_display_name 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 update_display_name completely? +

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

update_display_name is provided by the Poll MCP server (@solworks/poll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Poll tool call.

Deterministic rules across all 28 Poll tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.