update_beacon_signing_key · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_beacon_signing_key does on AdButler

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

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Beacon signing key ID
`key_name`	string	—	Beacon signing key name

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_beacon_signing_key needs a policy

This tool modifies an existing signing key, which is a critical security credential in ad tracking/reporting systems. While reversible (Write, not Destructive), updating beacon signing keys affects authentication and integrity verification of ad beacon requests across the AdButler platform. Misuse could redirect or forge beacon data, compromise tracking integrity, or enable unauthorized ad attribution changes.

From the tool's definition Tool name 'update_beacon_signing_key' and description 'Update an existing beacon signing key' indicate modification of security credentials used for beacon signing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_beacon_signing_key Rate-limited

update_beacon_signing_key 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": {
    "update_beacon_signing_key": {
      "limits": [
        {
          "counter": "update_beacon_signing_key_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 AdButler, so you can run agents against it safely.

FAQ

Questions about update_beacon_signing_key

What does the update_beacon_signing_key tool do? +

Update an existing beacon signing key. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_beacon_signing_key accept? +

update_beacon_signing_key accepts 2 parameters: id, key_name. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_beacon_signing_key? +

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

What risk level is update_beacon_signing_key? +

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

Can I rate-limit update_beacon_signing_key? +

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

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

update_beacon_signing_key is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.