Changes the execution order of an existing inbox rule
AI agents use edit-rule-sequence to create or update resources in Outlook Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook Assistant environment.
This tool modifies inbox rule settings by reordering their execution priority, which is a write operation that changes data/configuration state. It is reversible (rules can be resequenced again) and does not delete or destroy rules, so it does not qualify as Destructive. It is not Execute because it does not run code or trigger external operations—it only adjusts metadata.
From the tool's definition Tool name 'edit-rule-sequence' and description 'Changes the execution order of an existing inbox rule' indicate modification of existing rule configuration. The action is reversible (sequence can be changed again).
Attacks that exploit this kind of access
Changes the execution order of an existing inbox rule. It is categorised as a Write tool in the Outlook Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook Assistant MCP server in PolicyLayer and add a rule for edit-rule-sequence: 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 Outlook Assistant. Nothing to install.
edit-rule-sequence 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-rule-sequence 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-rule-sequence. 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-rule-sequence is provided by the Outlook Assistant MCP server (titanzero/outlook-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 →