Low Risk

query_components

Query components of a given type, optionally filtered.

How to control query_components ↓

AI agents call query_components 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.

Low Risk

This tool retrieves or queries data about energy system components without side effects. It falls squarely into the Read category as it performs data retrieval operations. The blast radius of misuse is minimal—an agent can only access information about existing components, not modify, delete, or execute operations on them.

From the tool's definition Tool name 'query_components' and description 'Query components of a given type, optionally filtered' indicate retrieval operations with no mention of modification, deletion, or execution of arbitrary code.

Documented attack patterns abuse exactly the kind of access query_components 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 query_components:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_components": {}
  }
}

query_components is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the query_components tool do? +

Query components of a given type, optionally filtered. It is categorised as a Read tool in the PyPSA MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_components? +

Register the PyPSA MCP server in PolicyLayer and add a rule for query_components: 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 query_components? +

query_components is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_components? +

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

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

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