dc_ups_battery_sizing
AI agents call dc_ups_battery_sizing to retrieve information from Datacenter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
UPS/battery sizing is a computational task that reads input parameters (power requirements, runtime needs, redundancy levels) and returns sizing recommendations. This aligns with the server's stated purpose of 'engineering calculations' and does not mutate state, execute arbitrary code, delete data, or move funds.
From the tool's definition Tool name 'dc_ups_battery_sizing' suggests it performs calculations or sizing recommendations for UPS and battery systems.
Attacks that exploit this kind of access
dc_ups_battery_sizing. It is categorised as a Read tool in the Datacenter MCP Server, which means it retrieves data without modifying state.
Register the Datacenter MCP server in PolicyLayer and add a rule for dc_ups_battery_sizing: 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 Datacenter. Nothing to install.
dc_ups_battery_sizing 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 dc_ups_battery_sizing 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 dc_ups_battery_sizing. 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.
dc_ups_battery_sizing is provided by the Datacenter MCP server (log-wade/datacenter-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 →