stateset_remove_component

Records removal of a component from a robot. Specify reason for removal (replacement, failure, upgrade).

SERVERStateset SOURCEstateset/stateset-mcp-server
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/stateset-mcp-server/stateset-remove-component.md

What stateset_remove_component does on Stateset

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

Why stateset_remove_component is rated Critical

Removing a component from a robot's record is a destructive action because it eliminates that component's association with the robot. While a reason like 'replacement' or 'upgrade' might imply a subsequent add, the removal itself cannot be undone without explicitly re-adding the component.

From the tool's definition 'Records removal of a component from a robot' — removal is an irreversible operation that deletes/detaches a physical or logical component from a robot's configuration.

Questions about stateset_remove_component

What does the stateset_remove_component tool do? +

Records removal of a component from a robot. Specify reason for removal (replacement, failure, upgrade). It is categorised as a Destructive tool in the Stateset 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 stateset_remove_component? +

Register the Stateset MCP server in PolicyLayer and add a rule for stateset_remove_component: 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 Stateset. Nothing to install.

What risk level is stateset_remove_component? +

stateset_remove_component 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 stateset_remove_component? +

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

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

stateset_remove_component is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Stateset, 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 Stateset'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.