remove_sharegroup_member
Revoke a membership token from a share group
This record as markdown: /tools/takashito-linode-mcp-server/remove-sharegroup-member.md
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.
Why remove_sharegroup_member is rated Critical
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
Attacks that exploit this kind of access
The rule that runs remove_sharegroup_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_sharegroup_member, this is the rule to start with:
remove_sharegroup_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every remove_sharegroup_member call is checked against it from then on.
Questions about remove_sharegroup_member
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.
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.
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.
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.
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.
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.
More on Linode MCP Server, and thousands of servers like it.
Across the catalogue