add_card_to_view
Add a card to a specific view in a dashboard.
This record as markdown: /tools/fistacho-ha-nexus-agent/add-card-to-view.md
What add_card_to_view does on Ha Nexus Agent
AI agents use add_card_to_view to create or update resources in Ha Nexus Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ha Nexus Agent environment.
Why add_card_to_view is rated Medium
This tool creates a new card widget in a Home Assistant dashboard view, which modifies the dashboard configuration reversibly. It falls under Write (creates/modifies data reversibly) rather than Execute or Destructive, as adding a card does not execute arbitrary code, delete data, or trigger external operations with unpredictable side effects.
From the tool's definition Tool name 'add_card_to_view' and description 'Add a card to a specific view in a dashboard' explicitly state creation/modification of dashboard configuration by adding a new card element.
Attacks that exploit this kind of access
The rule that runs add_card_to_view 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 add_card_to_view, this is the rule to start with:
add_card_to_view stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_card_to_view call is checked against it from then on.
Questions about add_card_to_view
Add a card to a specific view in a dashboard. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for add_card_to_view: 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.
add_card_to_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_card_to_view 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 add_card_to_view. 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.
add_card_to_view 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