AI agents use update_role to create or update resources in Defined — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defined environment.
This tool modifies (rather than deletes) role definitions in a network infrastructure management system. Role updates can affect access permissions and network behavior but are reversible via subsequent updates. The impact is significant in a network administration context (high severity), but it is a Write operation rather than Destructive since changes can be undone.
From the tool's definition Tool name 'update_role' indicates modification of role configurations. Sibling tools like 'create_role', 'add_firewall_rule', 'add_tag_config_override', and 'block_host' confirm this server manages access control and network permissions.
Attacks that exploit this kind of access
update_role. It is categorised as a Write tool in the Defined MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Defined MCP server in PolicyLayer and add a rule for update_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 Defined. Nothing to install.
update_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 update_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 update_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.
update_role is provided by the Defined MCP server (quickvm/defined-mcp). 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 →