delete_script_include

Delete a script include from ServiceNow

Server ServiceNow MCP Server shameerampcome/servicenow-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_script_include does on ServiceNow MCP Server

AI agents call delete_script_include to permanently remove resources in ServiceNow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_script_include needs a policy

This tool permanently removes a script include object from ServiceNow, which is a code artifact that likely supports workflows, automations, or integrations. Deletion cannot be undone without recovery from backups. While not as critical as deleting production data tables, removing script includes can break dependent processes and cause service disruptions.

From the tool's definition Tool name is 'delete_script_include' with description 'Delete a script include from ServiceNow'. The verb 'delete' combined with the action of removing a script include (code artifact) from the system indicates irreversible removal of data.

Questions about delete_script_include

What does the delete_script_include tool do? +

Delete a script include from ServiceNow. It is categorised as a Destructive tool in the ServiceNow MCP Server 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_script_include? +

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

What risk level is delete_script_include? +

delete_script_include 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_script_include? +

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

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

delete_script_include is provided by the ServiceNow MCP Server MCP server (shameerampcome/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.