Medium Risk

add_bus

add_bus

How to control add_bus ↓

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

Medium Risk

This tool creates a new entity (a bus node) in an energy system model, which is a reversible Write operation. It modifies the model state by adding data but does not execute arbitrary code, delete data irreversibly, or cause financial transactions.

From the tool's definition Tool name 'add_bus' and context within PyPSA MCP server (energy system modeling) indicate creation of a new bus component in an energy network model.

Documented attack patterns abuse exactly the kind of access add_bus gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PyPSA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_bus:

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

add_bus 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.

  1. Create a free account and register PyPSA MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the add_bus tool do? +

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

How do I enforce a policy on add_bus? +

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

What risk level is add_bus? +

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

Can I rate-limit add_bus? +

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

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

add_bus is provided by the PyPSA MCP server (open-energy-transition/pypsa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PyPSA MCP tool call.

Deterministic rules across all 22 PyPSA MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

22 PyPSA MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.