AI agents call get_number to retrieve information from Seven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about a phone number without creating, modifying, or deleting any data. It has no side effects and poses minimal risk if misused by an AI agent, as it only exposes existing phone number metadata.
From the tool's definition Tool name is 'get_number' and description states 'Get details of a specific active phone number' — retrieves data with no side effects.
Attacks that exploit this kind of access
Get details of a specific active phone number. It is categorised as a Read tool in the Seven MCP Server, which means it retrieves data without modifying state.
Register the Seven MCP server in PolicyLayer and add a rule for get_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.
get_number is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →