delete_css_custom_property

Delete a CSS custom property.

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

This record as markdown: /tools/fistacho-ha-nexus-agent/delete-css-custom-property.md

What delete_css_custom_property does on Ha Nexus Agent

AI agents call delete_css_custom_property to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_css_custom_property is rated Critical

The tool is explicitly named 'delete_*' and performs irreversible removal of configuration data (CSS custom property). While the blast radius is limited (CSS styling only, not core home automation functions), deletion operations are categorized as Destructive per the classification schema.

From the tool's definition delete_css_custom_property performs deletion of a CSS custom property, which cannot be undone without re-adding it manually.

Questions about delete_css_custom_property

What does the delete_css_custom_property tool do? +

Delete a CSS custom property. It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_css_custom_property? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for delete_css_custom_property: 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 delete_css_custom_property? +

delete_css_custom_property is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_css_custom_property? +

Yes. Add a rate_limit block to the delete_css_custom_property 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 delete_css_custom_property completely? +

Set action: deny in the PolicyLayer policy for delete_css_custom_property. 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 delete_css_custom_property? +

delete_css_custom_property 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.