Delete a company filter. DELETE /companies/filters/{filterId}. Required: filterId.
AI agents call remove_filter to permanently remove resources in Rebillia MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a filter is a destructive action that cannot be undone without recreating it. While the blast radius is limited to filter metadata rather than core financial or customer data, it permanently removes configuration and could disrupt business operations if filters are used for reporting, segmentation, or compliance purposes. This merits the Destructive category over Write.
From the tool's definition Tool description explicitly states "Delete a company filter" and uses HTTP DELETE method (/companies/filters/{filterId}), which is an irreversible operation.
Attacks that exploit this kind of access
Delete a company filter. DELETE /companies/filters/{filterId}. Required: filterId. It is categorised as a Destructive tool in the Rebillia MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for remove_filter: 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 Rebillia MCP Server. Nothing to install.
remove_filter 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 remove_filter 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 remove_filter. 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.
remove_filter is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). 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 →