get_automation_config
Get an automation's YAML config as a dict. Accepts bare id or 'automation.<id>'. Returns None if not found.
This record as markdown: /tools/fistacho-ha-nexus-agent/get-automation-config.md
What get_automation_config does on Ha Nexus Agent
AI agents call get_automation_config to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_automation_config is rated Low
This tool only reads and returns existing automation configuration in dictionary form. It has no side effects, cannot modify state, and poses minimal risk even if an AI agent calls it with arbitrary automation IDs. The worst case is retrieving sensitive configuration details that might be in automation definitions, but no destructive, financial, or execution-based risks apply.
From the tool's definition Tool description explicitly states 'Get an automation's YAML config' — retrieves/queries configuration data without modifying or executing anything. Returns None if not found, indicating pure data retrieval.
Attacks that exploit this kind of access
The rule that runs get_automation_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_automation_config, this is the rule to start with:
get_automation_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 Ha Nexus Agent, apply this rule, and every get_automation_config call is checked against it from then on.
Questions about get_automation_config
Get an automation's YAML config as a dict. Accepts bare id or 'automation.<id>'. Returns None if not found. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_automation_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 Ha Nexus Agent. Nothing to install.
get_automation_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 get_automation_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 get_automation_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.
get_automation_config is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue