identities_update_scopes · Mailgent MCP Server MCP

WHAT IT DOES

What identities_update_scopes does on Mailgent MCP Server

AI agents use identities_update_scopes to create or update resources in Mailgent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailgent MCP Server environment.

WHY IT NEEDS A POLICY

Why identities_update_scopes needs a policy

This tool modifies identity scopes, which are permission settings for email identities. While scopes can be added or removed (reversible), the action is a configuration change with potential security implications—an agent could expand scopes beyond intended access levels. Classified as Write rather than Execute because it modifies identity settings rather than executing arbitrary operations.

From the tool's definition Tool name 'identities_update_scopes' and description 'Add or remove scopes from an identity' indicate modification of identity permissions/configurations. This is a reversible write operation that changes what an identity can access or do.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identities_update_scopes Rate-limited

identities_update_scopes 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "identities_update_scopes": {
      "limits": [
        {
          "counter": "identities_update_scopes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mailgent MCP Server, so you can run agents against it safely.

FAQ

Questions about identities_update_scopes

What does the identities_update_scopes tool do? +

Add or remove scopes from an identity. It is categorised as a Write tool in the Mailgent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on identities_update_scopes? +

Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for identities_update_scopes: 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 Mailgent MCP Server. Nothing to install.

What risk level is identities_update_scopes? +

identities_update_scopes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit identities_update_scopes? +

Yes. Add a rate_limit block to the identities_update_scopes 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.

How do I block identities_update_scopes completely? +

Set action: deny in the PolicyLayer policy for identities_update_scopes. 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.

What MCP server provides identities_update_scopes? +

identities_update_scopes is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.