Delete documents matching a filter. Empty filters are rejected — pass at least one field.
AI agents call delete to permanently remove resources in Stripe Reporting — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the server being described as 'read-only' and not mutating Stripe state, this tool's name and description explicitly indicate it deletes documents. This is a destructive operation that cannot be undone. The presence of a delete function on what is otherwise a read-only reporting server is a major discrepancy and a critical security risk.
From the tool's definition Tool name is 'delete' and description states 'Delete documents matching a filter.' This is an irreversible data deletion operation.
Attacks that exploit this kind of access
Delete documents matching a filter. Empty filters are rejected — pass at least one field. It is categorised as a Destructive tool in the Stripe Reporting MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stripe Reporting MCP server in PolicyLayer and add a rule for 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 Stripe Reporting. Nothing to install.
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 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 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.
delete is provided by the Stripe Reporting MCP server (ohrytskov/stripe-reporting-mcp). 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 →