AI agents call get_metric_summary to retrieve information from ZStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves metric summaries from the ZStack Cloud monitoring system. This is a non-destructive data retrieval operation with no side effects. It does not modify state, execute arbitrary code, or perform financial transactions. The 'get' prefix in the name is a strong indicator of read-only semantics.
From the tool's definition Tool name 'get_metric_summary' indicates retrieval of metric summary data with no modification. Server description mentions 'query monitoring metrics and data' as a read operation.
Documented attack patterns abuse exactly the kind of access get_metric_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_metric_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_metric_summary": {}
}
}get_metric_summary 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_metric_summary. It is categorised as a Read tool in the ZStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZStack MCP Server MCP server in PolicyLayer and add a rule for get_metric_summary: 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 ZStack MCP Server. Nothing to install.
get_metric_summary 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_metric_summary 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_metric_summary. 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_metric_summary is provided by the ZStack MCP Server MCP server (zstackio/zstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ZStack 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.
6 ZStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.