user_settings

THE RISK

Medium Risk

Why user_settings needs a policy

This tool modifies user configuration data reversibly. While the description is incomplete (it mentions "two actions" without specifying them), the use of "manage" in a settings context typically means create/update operations rather than read-only access. Settings changes can have broad impact on system behavior and user workflows, warranting high severity.

From the tool's definition Tool description explicitly states "Manage user settings with two actions" - the verb "manage" combined with "settings" indicates modification capabilities.

Documented attack patterns abuse exactly the kind of access user_settings gives an agent:

POLICY

How to control user_settings

PolicyLayer is an MCP gateway — it sits between your AI agents and Microsoft Graph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for user_settings:

policy.json

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

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

Create a free account and register Microsoft Graph MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Microsoft Graph MCP Server tools

Destructive manage_emails Manage emails with multiple actions. Supports moving, deleting, archiving, flagging, and c Destructive manage_mail_folder Manage mail folders. Supports list, create, delete, rename, get_details, and move operatio Write manage_event_as_attendee Manage calendar events where you are an attendee (events organized by others). Actions: ac Write manage_event_as_organizer Manage calendar events where you are the organizer (events you created). Actions: create, Write manage_templates Manage email templates stored as drafts in a Templates folder. Templates are draft emails Write send_email Send emails directly without creating drafts. Supports three actions: Read browse_email_cache Browse emails in the cache with pagination. Returns summary information with number column Read browse_events Browse calendar events in the cache with pagination. Returns summary information with numb

All 19 Microsoft Graph MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about user_settings

What does the user_settings tool do? +

Manage user settings with two actions:. It is categorised as a Write tool in the Microsoft Graph 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 user_settings? +

Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for user_settings: 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.

What risk level is user_settings? +

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

Can I rate-limit user_settings? +

Yes. Add a rate_limit block to the user_settings 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 user_settings completely? +

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

user_settings is provided by the Microsoft Graph MCP Server MCP server (marlonluo2018/microsoft_graph_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Microsoft Graph MCP Server tool call.

Start from Microsoft Graph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →