set_cleanup_rule_active
Activate or deactivate a Table Cleanup Rule. Activation requires confirmation; matching live records are permanently deleted. [Destructive]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/set-cleanup-rule-active.md
What set_cleanup_rule_active does on ServiceNow-MCP
AI agents call set_cleanup_rule_active to permanently remove resources in ServiceNow-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why set_cleanup_rule_active is rated Critical
Activating cleanup rules irreversibly deletes matching records without undo capability.
From the tool's definition permanently deleted
Attacks that exploit this kind of access
The rule that runs set_cleanup_rule_active safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_cleanup_rule_active, this is the rule to start with:
set_cleanup_rule_active 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 ServiceNow-MCP, apply this rule, and every set_cleanup_rule_active call is checked against it from then on.
Questions about set_cleanup_rule_active
Activate or deactivate a Table Cleanup Rule. Activation requires confirmation; matching live records are permanently deleted. [Destructive]. It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP server in PolicyLayer and add a rule for set_cleanup_rule_active: 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 ServiceNow-MCP. Nothing to install.
set_cleanup_rule_active 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 set_cleanup_rule_active 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 set_cleanup_rule_active. 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.
set_cleanup_rule_active is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
Across the catalogue