AI agents use update_number to create or update resources in Seven — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Seven environment.
This tool modifies phone number settings (friendly name, forwarding) reversibly without deleting data or executing arbitrary code. It falls under Write category as a configuration update. Severity is medium because misconfiguration could disrupt communications or redirect calls/messages to unintended destinations, but the action is reversible and confined to a specific phone number's settings.
From the tool's definition Tool name 'update_number' and description 'Update phone number configuration including friendly name and forwarding settings' indicate modification of existing configuration data.
Attacks that exploit this kind of access
Update phone number configuration including friendly name and forwarding settings. It is categorised as a Write tool in the Seven MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Seven MCP server in PolicyLayer and add a rule for update_number: 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 Seven. Nothing to install.
update_number 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_number 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_number. 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_number is provided by the Seven MCP server (seven-io/seven-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 →