This record as markdown: /tools/io-github-devopam-mcpg/drop-graph.md
What drop_graph does on Mcpg
AI agents call drop_graph to permanently remove resources in Mcpg, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why drop_graph is rated Critical
The name 'drop_graph' strongly indicates permanent removal of a graph object. Despite the missing description, the semantics of 'drop' in SQL/database contexts universally means irreversible deletion. In a production PostgreSQL environment, this could destroy application-critical data without recovery options. Severity is critical due to the production-grade context and blast radius of data loss.
From the tool's definition Tool name 'drop_graph' with empty description suggests irreversible deletion of a graph data structure in PostgreSQL. In a production database context, 'drop' is a canonical destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs drop_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drop_graph, this is the rule to start with:
drop_graph 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 Mcpg, apply this rule, and every drop_graph call is checked against it from then on.
Questions about drop_graph
drop_graph is a destructive tool on the Mcpg MCP server. It is categorised as a Destructive tool in the Mcpg MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcpg MCP server in PolicyLayer and add a rule for drop_graph: 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 Mcpg. Nothing to install.
drop_graph 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 drop_graph 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 drop_graph. 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.
drop_graph is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
Across the catalogue