Permanently delete one or more documents by their IDs. This action CANNOT be undone. All sections and content within the deleted documents will also be permanently removed. Args: - document_ids (number[], required): Array of document IDs to delete (minimum 1) Returns: Confirmation of deletion wit...
AI agents call itglue_delete_documents to permanently remove resources in Itglue — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data with no undo capability, fitting the Destructive category definition. While not financial, the permanent removal of potentially critical ITGlue documentation (which typically contains sensitive IT infrastructure, credentials, and operational records) represents a high-severity risk if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Permanently delete one or more documents' and 'This action CANNOT be undone.' The tool removes documents and 'All sections and content within the deleted documents will also be permanently removed.'
Documented attack patterns abuse exactly the kind of access itglue_delete_documents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Itglue, and nothing reaches the server without passing your rules. This is the rule we recommend for itglue_delete_documents:
{
"version": "1",
"default": "deny",
"hide": [
"itglue_delete_documents"
]
} itglue_delete_documents disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete one or more documents by their IDs. This action CANNOT be undone. All sections and content within the deleted documents will also be permanently removed. Args: - document_ids (number[], required): Array of document IDs to delete (minimum 1) Returns: Confirmation of deletion with the list of deleted IDs. Examples: -. It is categorised as a Destructive tool in the Itglue MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Itglue MCP server in PolicyLayer and add a rule for itglue_delete_documents: 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 Itglue. Nothing to install.
itglue_delete_documents 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 itglue_delete_documents 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 itglue_delete_documents. 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.
itglue_delete_documents is provided by the Itglue MCP server (junto-platforms/itglue-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Itglue, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Itglue tools catalogued and risk-classified — across an index of 43,000+ MCP servers.