AI agents call list_specifications 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 only retrieves and displays specification data from a construction project document. It performs no write, execute, destructive, or financial operations. The server itself is described as 'read-only', confirming no side effects are possible. The blast radius of misuse is minimal—an agent could only access existing specification information.
From the tool's definition Tool name 'list_specifications' and description explicitly state it 'List all specifications' and 'Returns IDs, descriptions, quantities, units, and tags' — purely retrieving/querying data with no modification capability.
Attacks that exploit this kind of access
List all specifications of a given lot. Specifications are the detailed line items of the DPGF (project bid document). Returns IDs, descriptions, quantities, units, and tags. 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_specifications: 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_specifications 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_specifications 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_specifications. 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_specifications 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 →