[Deprecated] Set time snapshots. Use configure_time(mode='snapshots') instead.
AI agents use set_snapshots 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 time snapshot settings within a PyPSA energy model, which is a reversible data modification operation (Write category). Severity is low because: (1) it only affects temporal configuration metadata, not core system data; (2) changes are reversible via re-configuration; (3) no external side effects or financial impact; (4) the tool is explicitly deprecated, reducing likelihood of active…
From the tool's definition Tool name 'set_snapshots' and description indicating it 'Set[s] time snapshots' modifies time-related configuration in an energy system model.
Documented attack patterns abuse exactly the kind of access set_snapshots 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 set_snapshots:
{
"version": "1",
"default": "deny",
"tools": {
"set_snapshots": {
"limits": [
{
"counter": "set_snapshots_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_snapshots 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.
[Deprecated] Set time snapshots. Use configure_time(mode='snapshots') instead. 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 set_snapshots: 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.
set_snapshots 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 set_snapshots 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 set_snapshots. 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.
set_snapshots 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.