Access Groups \u00b7 mutation deleteRole. Variables: id. Example variables: {\
AI agents call delete_role to permanently remove resources in ReliaQuest GreyMatter MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_role' tool permanently removes an access control role from the system. This is a destructive operation that cannot be easily undone and affects system security posture by removing user permission structures.
From the tool's definition Tool name 'delete_role' with mutation operation on access control. The description explicitly states 'mutation deleteRole' indicating an irreversible deletion operation in the access control domain.
Attacks that exploit this kind of access
Access Groups \u00b7 mutation deleteRole. Variables: id. Example variables: {\. It is categorised as a Destructive tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for delete_role: 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 ReliaQuest GreyMatter MCP Server. Nothing to install.
delete_role 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 delete_role 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 delete_role. 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.
delete_role is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-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 →