AI agents call get_statistics to retrieve information from PyPSA MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty, the tool name 'get_statistics' clearly indicates a retrieval operation that queries and returns aggregate information about an energy system model. No language suggests side effects, data modification, execution of external operations, or destructive actions.
From the tool's definition Tool named 'get_statistics' with no description provided. The name strongly suggests data retrieval/querying of statistical information about an energy system model, consistent with read-only operations.
Documented attack patterns abuse exactly the kind of access get_statistics 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 get_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_statistics": {}
}
}get_statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_statistics. It is categorised as a Read tool in the PyPSA MCP MCP Server, which means it retrieves data without modifying state.
Register the PyPSA MCP server in PolicyLayer and add a rule for get_statistics: 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.
get_statistics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_statistics 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 get_statistics. 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.
get_statistics 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.