config
Return Home Assistant core configuration.
This record as markdown: /tools/mcp-control-plane/config.md
What config does on Mcp Control Plane
AI agents call config to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why config is rated Low
This tool retrieves configuration information from Home Assistant without creating, modifying, deleting, or executing any operations. It is a read-only query that returns static configuration data. The blast radius is minimal—misconfiguration disclosure could expose architecture details but would not directly compromise systems or trigger unintended actions.
From the tool's definition Tool name 'config' and description 'Return Home Assistant core configuration' indicate retrieval of existing configuration data without modification or execution.
Attacks that exploit this kind of access
The rule that runs config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For config, this is the rule to start with:
config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every config call is checked against it from then on.
Questions about config
Return Home Assistant core configuration. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for config: 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 Mcp Control Plane. Nothing to install.
config 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 config 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 config. 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.
config is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue