AI agents use add_component 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.
This tool creates or modifies energy system model data by adding components. While the description is empty (reducing confidence slightly), the naming pattern and context of sibling 'add_*' tools strongly suggest it performs Write operations (creating new model components). This is reversible (can be undone via delete or model recreation) and has no irreversible side effects, placing it in the Write category.
From the tool's definition Tool name 'add_component' indicates creation of a new component. Sibling tools include 'add_bus', 'add_generator', 'add_line', 'add_load' which are all Write operations that create/add reversible data structures to energy models.
Documented attack patterns abuse exactly the kind of access add_component 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_component:
{
"version": "1",
"default": "deny",
"tools": {
"add_component": {
"limits": [
{
"counter": "add_component_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_component 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.
Free to start. No card required.
add_component. 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.
Register the PyPSA MCP server in PolicyLayer and add a rule for add_component: 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.
add_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_component 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.
Set action: deny in the PolicyLayer policy for add_component. 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.
add_component 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.
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.