Revoke a user
AI agents call remove_user_from_agent to permanently remove resources in MoluAbi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a user's access is a destructive operation — it removes an established relationship or permission that may not be easily restored. The sibling tool 'add_user_to_agent' could theoretically re-add the user, but revocation itself is an access-removal action with potentially significant impact (loss of access, data, or permissions).
From the tool's definition Tool name 'remove_user_from_agent' and description 'Revoke a user' indicate removal of a user's access from an agent, which is an irreversible revocation action.
Attacks that exploit this kind of access
Revoke a user. It is categorised as a Destructive tool in the MoluAbi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for remove_user_from_agent: 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 MoluAbi MCP Server. Nothing to install.
remove_user_from_agent 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_user_from_agent 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_user_from_agent. 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_user_from_agent is provided by the MoluAbi MCP Server MCP server (oregpt/moluabi-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 →