Remove a member from a scope (requires authentication and scope admin).
AI agents call jsr_remove_scope_member to permanently remove resources in JSR MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a member from a scope is an irreversible access-control action — the member loses their permissions and association with the scope immediately. This cannot be automatically undone (re-adding requires a new invite/admin action).
From the tool's definition Remove a member from a scope
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Remove a member from a scope (requires authentication and scope admin). It is categorised as a Destructive tool in the JSR MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JSR MCP server in PolicyLayer and add a rule for jsr_remove_scope_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 JSR MCP. Nothing to install.
jsr_remove_scope_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 jsr_remove_scope_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 jsr_remove_scope_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.
jsr_remove_scope_member is provided by the JSR MCP server (wyattjoh/jsr-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 →