Destroy an existing browser session in Scrappey to free resources
AI agents call scrappey_destroy_session to permanently remove resources in Scrappey MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly terminates a browser session, preventing further use of that session. While the data loss is limited to the session itself (not user data), the action is permanent and cannot be undone. This qualifies as Destructive rather than Write.
From the tool's definition Tool name contains 'destroy' and description states 'Destroy an existing browser session' - explicit termination of a resource that cannot be reversed
Attacks that exploit this kind of access
Destroy an existing browser session in Scrappey to free resources. It is categorised as a Destructive tool in the Scrappey MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scrappey MCP Server MCP server in PolicyLayer and add a rule for scrappey_destroy_session: 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 Scrappey MCP Server. Nothing to install.
scrappey_destroy_session 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 scrappey_destroy_session 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 scrappey_destroy_session. 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.
scrappey_destroy_session is provided by the Scrappey MCP Server MCP server (pim97/mcp-server-scrappey). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →