AI agents use edit_role to create or update resources in Superglue MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superglue MCP environment.
This tool modifies role configurations, which could affect access control and permissions across integrated systems. While not irreversible (roles can be re-edited), the ability to change role permissions represents a significant security-relevant write operation with potential blast radius.
From the tool's definition Tool name is 'edit_role' and description states 'Edit a role'. The verb 'edit' indicates modification of existing data (role definitions).
Documented attack patterns abuse exactly the kind of access edit_role gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Superglue MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for edit_role:
{
"version": "1",
"default": "deny",
"tools": {
"edit_role": {
"limits": [
{
"counter": "edit_role_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_role stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Edit a role. It is categorised as a Write tool in the Superglue MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Superglue MCP server in PolicyLayer and add a rule for edit_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 Superglue MCP. Nothing to install.
edit_role is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit_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 edit_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.
edit_role is provided by the Superglue MCP server (superglue-ai/superglue). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Superglue MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Superglue MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.