Permanently delete a document section by its ID. This action CANNOT be undone. The section and all its content will be permanently removed from the parent document. Args: - document_id (number, required): The parent document ID - section_id (number, required): The section ID to delete Returns: Co...
AI agents call itglue_delete_document_section 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.
The tool permanently removes document sections and their content with no possibility of reversal. This is a destructive operation that irreversibly deletes data. While not as critical as financial operations, the permanent loss of documentation in an IT asset management system (ITGlue) could have significant operational impact.
From the tool's definition "Permanently delete a document section by its ID. This action CANNOT be undone." The tool explicitly deletes data irreversibly with no undo capability.
Documented attack patterns abuse exactly the kind of access itglue_delete_document_section 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_document_section:
{
"version": "1",
"default": "deny",
"hide": [
"itglue_delete_document_section"
]
} itglue_delete_document_section 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 a document section by its ID. This action CANNOT be undone. The section and all its content will be permanently removed from the parent document. Args: - document_id (number, required): The parent document ID - section_id (number, required): The section ID to delete Returns: Confirmation of successful deletion. 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_document_section: 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_document_section 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_document_section 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_document_section. 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_document_section 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.