AI agents call list_schedules to retrieve information from Trane without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schedule data from a building automation system without creating, modifying, deleting, or executing any operations. It is a simple inventory query that returns static or near-static schedule information, posing minimal risk even if misused by an agent.
From the tool's definition Tool description states 'Inventory operating schedules' and the server is documented as providing 'read access' for 'inventory and telemetry retrieval.' The tool name 'list_schedules' and usage context ('planning around occupancy or seasonal modes') confirm…
Attacks that exploit this kind of access
Inventory operating schedules for buildings + equipment. Used by an agent planning around occupancy or seasonal modes. It is categorised as a Read tool in the Trane MCP Server, which means it retrieves data without modifying state.
Register the Trane MCP server in PolicyLayer and add a rule for list_schedules: 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 Trane. Nothing to install.
list_schedules 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_schedules 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_schedules. 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_schedules is provided by the Trane MCP server (nobanks/trane-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 →