Low Risk

devbox_poll_all

Poll all active runs across all projects in one call. Returns status of every run that is queued, planning, executing, awaiting_delegation, or awaiting_approval. Use at turn start to discover runs needing attention.

Risk signalsBulk/mass operation — affects multiple targets

Part of the Devbox server.

devbox_poll_all is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DEVBOX →

Free to start. No card required.

AI agents call devbox_poll_all to retrieve information from Devbox without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though devbox_poll_all only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "devbox_poll_all": {}
  }
}

See the full Devbox policy for all 38 tools.

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

ENFORCE ON MY DEVBOX →

View all 38 tools →

These attack patterns abuse exactly the kind of access devbox_poll_all 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 devbox_poll_all only ever does what you allow.

SECURE DEVBOX →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the devbox_poll_all tool do? +

Poll all active runs across all projects in one call. Returns status of every run that is queued, planning, executing, awaiting_delegation, or awaiting_approval. Use at turn start to discover runs needing attention.. It is categorised as a Read tool in the Devbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on devbox_poll_all? +

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

What risk level is devbox_poll_all? +

devbox_poll_all is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit devbox_poll_all? +

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

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

devbox_poll_all is provided by the Devbox MCP server (devbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Devbox tool call.

Deterministic rules across all 38 Devbox 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.