Get power consumption statistics for servers or chassis
AI agents call get_power_statistics to retrieve information from Intersight MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves telemetry data (power consumption metrics) from Intersight for monitoring purposes. It has no side effects, does not create, modify, or delete infrastructure configuration, and does not execute commands or trigger operational changes.
From the tool's definition Tool name and description indicate 'Get power consumption statistics' — a retrieval operation with no modification, deletion, or execution of external operations. The verb 'Get' and the passive noun 'statistics' confirm a read-only query.
Documented attack patterns abuse exactly the kind of access get_power_statistics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intersight MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_power_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_power_statistics": {}
}
} get_power_statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get power consumption statistics for servers or chassis. It is categorised as a Read tool in the Intersight MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intersight MCP Server MCP server in PolicyLayer and add a rule for get_power_statistics: 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 Intersight MCP Server. Nothing to install.
get_power_statistics 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_power_statistics 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_power_statistics. 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_power_statistics is provided by the Intersight MCP Server MCP server (jim-coyne/intersight_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intersight MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
198 Intersight MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.