Remove a permission from a SharePoint site
AI agents call remove_site_permission to permanently remove resources in Microsoft Graph MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a site permission destructively revokes access and deletes the permission configuration. While the underlying user account and site remain, the specific permission artifact is permanently deleted. This is classified as Destructive rather than Write because the operation cannot be reversed by simple overwriting—restoring access requires explicit re-granting.
From the tool's definition Tool performs 'Remove a permission' operation on a SharePoint site, which is an irreversible deletion of access rights. The action cannot be undone without re-granting the permission.
Attacks that exploit this kind of access
Remove a permission from a SharePoint site. It is categorised as a Destructive tool in the Microsoft Graph MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for remove_site_permission: 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 Microsoft Graph MCP Server. Nothing to install.
remove_site_permission 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_site_permission 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_site_permission. 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_site_permission is provided by the Microsoft Graph MCP Server MCP server (ry-ops/microsoft-graph-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 →