delete_instance_knowledge
Delete a knowledge document from your private subscribed instance.
This record as markdown: /tools/io-github-proagentstore-platform/delete-instance-knowledge.md
What delete_instance_knowledge does on ProAgentStore
AI agents call delete_instance_knowledge to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_instance_knowledge is rated Critical
The tool performs an irreversible deletion operation on knowledge documents. This is a Destructive action (cannot be undone), which ranks higher in severity than Write or Execute. High severity because inadvertent deletion of knowledge documents could impact business operations and data integrity, though blast radius is somewhat limited to a private instance rather than shared/production data.
From the tool's definition Tool name contains 'delete' and description states 'Delete a knowledge document from your private subscribed instance' — this irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs delete_instance_knowledge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_instance_knowledge, this is the rule to start with:
delete_instance_knowledge 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 ProAgentStore, apply this rule, and every delete_instance_knowledge call is checked against it from then on.
Questions about delete_instance_knowledge
Delete a knowledge document from your private subscribed instance. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for delete_instance_knowledge: 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 ProAgentStore. Nothing to install.
delete_instance_knowledge 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 delete_instance_knowledge 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 delete_instance_knowledge. 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.
delete_instance_knowledge is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue