revoke_people_share_link
Disable the People database public share link; the URL stops working. Admin only.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/revoke-people-share-link.md
What revoke_people_share_link does on Max MCP Server
AI agents call revoke_people_share_link to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why revoke_people_share_link is rated Critical
Irreversibly disables a share link, breaking existing access for all users.
From the tool's definition Disable the People database public share link; the URL stops working
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs revoke_people_share_link safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_people_share_link, this is the rule to start with:
revoke_people_share_link 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 Max MCP Server, apply this rule, and every revoke_people_share_link call is checked against it from then on.
Questions about revoke_people_share_link
Disable the People database public share link; the URL stops working. Admin only. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for revoke_people_share_link: 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 Max MCP Server. Nothing to install.
revoke_people_share_link 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_people_share_link 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_people_share_link. 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_people_share_link is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue