stateset_remove_component
Records removal of a component from a robot. Specify reason for removal (replacement, failure, upgrade).
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.
Attacks that exploit this kind of access
The rule that runs stateset_remove_component safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_remove_component, this is the rule to start with:
stateset_remove_component is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_remove_component call is checked against it from then on.
Questions about stateset_remove_component
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.
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.
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.
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.
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.
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.
Across the catalogue