AI agents call list_locations to retrieve information from Raygister without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries construction project location data (rooms, floors, zones) with no side effects. It performs a simple data retrieval operation consistent with the 'Read' category. The read-only nature of the server and the passive retrieval semantics (list, return) confirm this classification.
From the tool's definition Tool description explicitly states it 'List[s] all locations' and 'Returns location IDs, names, floor numbers, and parent location IDs'. The server itself is marked 'Read-only MCP server'. No mutation, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
List all locations (rooms, floors, zones) of a project. Returns location IDs, names, floor numbers, and parent location IDs for hierarchy. The response is a flat list, not paginated. It is categorised as a Read tool in the Raygister MCP Server, which means it retrieves data without modifying state.
Register the Raygister MCP server in PolicyLayer and add a rule for list_locations: 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 Raygister. Nothing to install.
list_locations 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 list_locations 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 list_locations. 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.
list_locations is provided by the Raygister MCP server (raygisterinc/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 →