update_script_button · PyNet Bridge MCP: Risk & Policy

WHAT IT DOES

What update_script_button does on PyNet Bridge

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

WHY IT NEEDS A POLICY

Why update_script_button needs a policy

This tool modifies existing configuration data (metadata and module placement) without deleting anything or executing arbitrary code. Updates are typically reversible, making this a Write-category tool. Severity is medium because misuse could corrupt UI configuration or move critical buttons to unexpected locations, but the effects are confined to metadata and are potentially recoverable.

From the tool's definition Tool description states it 'Updates metadata for an existing ScriptButton or moves it to another module' — the action of updating metadata is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_script_button Rate-limited

update_script_button 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_script_button": {
      "limits": [
        {
          "counter": "update_script_button_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 PyNet Bridge, so you can run agents against it safely.

FAQ

Questions about update_script_button

What does the update_script_button tool do? +

Updates metadata for an existing ScriptButton or moves it to another module. It is categorised as a Write tool in the PyNet Bridge 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_script_button? +

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

What risk level is update_script_button? +

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

Can I rate-limit update_script_button? +

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

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

update_script_button is provided by the PyNet Bridge MCP server (rafael-nunezdearenas/pynetbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.