AI agents call compare_coolants to retrieve information from Thermal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs thermal analysis and comparison—a computational read operation that simulates or queries performance characteristics of different coolant types. There are no side effects: it does not execute control commands, modify coolant systems, adjust hardware settings, delete data, or trigger financial transactions. The tool is purely informational and analytical, making it a Read category with low severity.
From the tool's definition The tool name 'compare_coolants' and description 'Compare thermal and hydraulic performance of water vs 50/50 glycol under identical conditions' indicate a query/analysis operation that retrieves or computes comparative data without modifying any system…
Attacks that exploit this kind of access
Compare thermal and hydraulic performance of water vs 50/50 glycol under identical conditions. It is categorised as a Read tool in the Thermal MCP Server, which means it retrieves data without modifying state.
Register the Thermal MCP server in PolicyLayer and add a rule for compare_coolants: 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 Thermal. Nothing to install.
compare_coolants 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 compare_coolants 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 compare_coolants. 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.
compare_coolants is provided by the Thermal MCP server (riccardovietri/thermal-mcp-server). 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 →