Critical Risk →

remove_sharegroup_member

Revoke a membership token from a share group

How to control remove_sharegroup_member ↓

What remove_sharegroup_member does on Linode MCP Server

AI agents call remove_sharegroup_member to permanently remove resources in Linode MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_sharegroup_member needs a policy

Revoking a membership token is an irreversible removal action — once the token is revoked, the member loses access and the token is invalidated. This cannot be undone without re-issuing/re-adding the member, making it a destructive operation. The blast radius is high because it can cut off access to shared cloud resources for the affected member.

From the tool's definition Revoke a membership token from a share group

Documented attack patterns abuse exactly the kind of access remove_sharegroup_member gives an agent:

How to control remove_sharegroup_member

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_sharegroup_member:

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

remove_sharegroup_member disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_sharegroup_member

What does the remove_sharegroup_member tool do? +

Revoke a membership token from a share group. It is categorised as a Destructive tool in the Linode MCP Server 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 remove_sharegroup_member? +

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

What risk level is remove_sharegroup_member? +

remove_sharegroup_member 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 remove_sharegroup_member? +

Yes. Add a rate_limit block to the remove_sharegroup_member 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 remove_sharegroup_member completely? +

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

remove_sharegroup_member is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, 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.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.