Describe the full input-parameter schema for a PyPSA component type.
AI agents call describe_component 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.
This tool retrieves and returns metadata/schema information about PyPSA component types. It has no side effects, does not execute code, does not modify the energy model, and does not trigger external operations. It is a pure read operation that fetches descriptive data, making it appropriate for the 'Read' category with low severity and high confidence.
From the tool's definition Tool name is 'describe_component' and description states it 'Describe[s] the full input-parameter schema for a PyPSA component type' — a retrieval operation that queries and returns schema information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access describe_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 describe_component:
{
"version": "1",
"default": "deny",
"tools": {
"describe_component": {}
}
}describe_component 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.
Describe the full input-parameter schema for a PyPSA component type. 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 describe_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.
describe_component 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 describe_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 describe_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.
describe_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.