AI agents call list_lots 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 construction project lot information without any side effects, modifications, or state changes. It is a standard list/query operation that returns reference data (IDs, types, names, statuses) to enable further lookups. The read-only server designation and lack of any write, delete, execute, or financial operations confirm low severity.
From the tool's definition Tool description explicitly states 'List all lots' and 'Returns lot IDs, types, names, and statuses' - purely retrieves and queries data with no modification. Server description confirms 'Read-only MCP server'.
Attacks that exploit this kind of access
List all lots (work packages) of a given project. Returns lot IDs, types (e.g. plumbing, HVAC), names, and statuses. Use the lot IDs to fetch specifications or full lot details. 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_lots: 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_lots 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_lots 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_lots. 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_lots 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 →