set_burst_opt_in

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-echorelay-management/set-burst-opt-in.md

WHAT IT DOES

What set_burst_opt_in does on EchoRelay

AI agents use set_burst_opt_in to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.

Parameter	Type	Required	Description
`enabled`	boolean	Yes	true to enable the burst window; false to disable.

Parameters from the server's own tool schema.

RISK

Why set_burst_opt_in is rated Medium

An AI agent can call set_burst_opt_in faster than any human can review: one bad instruction and it creates or modifies resources in EchoRelay by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_burst_opt_in safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EchoRelay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_burst_opt_in, this is the rule to start with:

set_burst_opt_in Rate-limited

set_burst_opt_in 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": {
    "set_burst_opt_in": {
      "limits": [
        {
          "counter": "set_burst_opt_in_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every set_burst_opt_in call is checked against it from then on.

FAQ

Questions about set_burst_opt_in

What does the set_burst_opt_in tool do? +

Enable or disable the auto-decaying burst window for live traffic and publish the change immediately. When enabled, brief spikes a little above your steady RPM cap are absorbed at the normal credit rate (no surcharge, no burst SKU) instead of being rejected. Sustained overage decays back to your steady cap; headroom returns once traffic cools below the cap or you add RPM. Burst usage is tracked so you can see when to upgrade. Default is off (steady cap is a hard 429). Requires edit access. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does set_burst_opt_in accept? +

set_burst_opt_in accepts 1 parameter: enabled. Required: enabled. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_burst_opt_in? +

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

What risk level is set_burst_opt_in? +

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

Can I rate-limit set_burst_opt_in? +

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

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

set_burst_opt_in is provided by the EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EchoRelay, and thousands of servers like it.

This server

All 78 EchoRelay tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →