This record as markdown: /tools/app-businys-mcp-server/revoke-portal-access.md
What revoke_portal_access does on Businys
AI agents call revoke_portal_access to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why revoke_portal_access is rated Critical
Revoking access is a destructive, difficult-to-undo action that cuts off a client's ability to interact with their portal. The description is truncated but the action name and partial description clearly indicate removal of access privileges. Misuse could sever client relationships and disrupt ongoing engagements, warranting a high severity rating.
From the tool's definition 'Revoke a client' — revoking portal access is an irreversible removal of access rights for a client
Attacks that exploit this kind of access
The rule that runs revoke_portal_access safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_portal_access, this is the rule to start with:
revoke_portal_access 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 Businys, apply this rule, and every revoke_portal_access call is checked against it from then on.
Questions about revoke_portal_access
Revoke a client. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for revoke_portal_access: 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 Businys. Nothing to install.
revoke_portal_access 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 revoke_portal_access 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 revoke_portal_access. 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.
revoke_portal_access is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue