AI agents call lookup_hlr 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.
HLR (Home Location Register) lookup is a standard telecom operation that queries carrier databases to retrieve metadata about a phone number (network operator, roaming status, validity). It has no side effects, creates no modifications, executes no code, and incurs no financial transactions. The tool retrieves information only, making it a Read-category risk with low severity due to limited blast radius if misused.
From the tool's definition Tool name 'lookup_hlr' and description 'Perform Home Location Register lookup (network info, roaming status)' indicate a read-only query operation that retrieves network information about a phone number without modifying any data.
Attacks that exploit this kind of access
Perform Home Location Register lookup (network info, roaming status). 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 lookup_hlr: 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.
lookup_hlr 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 lookup_hlr 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 lookup_hlr. 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.
lookup_hlr 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 →