Create a new PyPSA energy model with the given ID.
AI agents use create_energy_model 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.
The tool creates a new energy model object, which is a reversible write operation. There are no side effects beyond model instantiation, no code execution, no data deletion, and no financial implications. Severity is low because misuse results in creation of benign simulation data that can be easily deleted.
From the tool's definition Tool name 'create_energy_model' and description 'Create a new PyPSA energy model' indicate data creation. This is reversible via the sibling tool 'delete_model', confirming Write rather than Destructive.
Documented attack patterns abuse exactly the kind of access create_energy_model 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 create_energy_model:
{
"version": "1",
"default": "deny",
"tools": {
"create_energy_model": {
"limits": [
{
"counter": "create_energy_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_energy_model 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.
Create a new PyPSA energy model with the given ID. 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 create_energy_model: 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.
create_energy_model 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 create_energy_model 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 create_energy_model. 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.
create_energy_model 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.