add_card_to_view

Add a card to a specific view in a dashboard.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about add_card_to_view

What does the add_card_to_view tool do? +

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.

How do I enforce a policy on add_card_to_view? +

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.

What risk level is add_card_to_view? +

add_card_to_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_card_to_view? +

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.

How do I block add_card_to_view completely? +

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.

What MCP server provides add_card_to_view? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.