AI agents call get_equipment 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 queries and returns metadata about a building automation system component. It is purely informational with no capability to modify system state, execute commands, or cause irreversible changes.
From the tool's definition Tool name is 'get_equipment' and description states it retrieves 'full metadata for a single equipment unit'.
Attacks that exploit this kind of access
Get full metadata for a single equipment unit including current health flags, model, and linked points. 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 get_equipment: 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.
get_equipment 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 get_equipment 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 get_equipment. 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.
get_equipment 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 →