Critical Risk →

leave_all_roles

Remove a specified member from all roles in the application.

Part of the FlowSheets server.

leave_all_roles can permanently delete data in FlowSheets, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FLOWSHEETS →

Free to start. No card required.

AI agents may call leave_all_roles to permanently remove or destroy resources in FlowSheets. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call leave_all_roles in a loop, permanently destroying resources in FlowSheets. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "leave_all_roles"
  ]
}

See the full FlowSheets policy for all 36 tools.

Get this rule live on your own FlowSheets server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FLOWSHEETS →

View all 36 tools →

These attack patterns abuse exactly the kind of access leave_all_roles gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so leave_all_roles only ever does what you allow.

SECURE FLOWSHEETS →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the leave_all_roles tool do? +

Remove a specified member from all roles in the application.. It is categorised as a Destructive tool in the FlowSheets MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on leave_all_roles? +

Register the FlowSheets MCP server in PolicyLayer and add a rule for leave_all_roles: 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 FlowSheets. Nothing to install.

What risk level is leave_all_roles? +

leave_all_roles is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit leave_all_roles? +

Yes. Add a rate_limit block to the leave_all_roles 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.

How do I block leave_all_roles completely? +

Set action: deny in the PolicyLayer policy for leave_all_roles. 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.

What MCP server provides leave_all_roles? +

leave_all_roles is provided by the FlowSheets MCP server (garfield-bb/hap_paas2025). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FlowSheets tool call.

Deterministic rules across all 36 FlowSheets tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.