AI agents call monitor_delete to permanently remove resources in Scrapegraph — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a monitor resource. Deletion is irreversible and cannot be undone, placing it in the Destructive category. Severity is high because deleting a monitor would remove all associated monitoring configuration and potentially historical data, with no recovery path described.
From the tool's definition 'Delete a monitor' and 'DELETE /monitor/:id' — explicitly removes a monitor resource via HTTP DELETE
Documented attack patterns abuse exactly the kind of access monitor_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scrapegraph, and nothing reaches the server without passing your rules. This is the rule we recommend for monitor_delete:
{
"version": "1",
"default": "deny",
"hide": [
"monitor_delete"
]
}monitor_delete 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.
Delete a monitor (API v2 DELETE /monitor/:id). It is categorised as a Destructive tool in the Scrapegraph MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scrapegraph MCP server in PolicyLayer and add a rule for monitor_delete: 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 Scrapegraph. Nothing to install.
monitor_delete 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 monitor_delete 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 monitor_delete. 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.
monitor_delete is provided by the Scrapegraph MCP server (ScrapeGraphAI/scrapegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Scrapegraph, 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.
17 Scrapegraph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.