Get metrics history timeline (up to 60 data points at 5-second intervals).
AI agents call get_metrics_history to retrieve information from Overlord 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 historical metrics data within a bounded timeframe (60 data points at 5-second intervals). It is a passive query operation that reads existing data without side effects, making it a Read category tool. Within the context of a C2 framework (command and control), metrics history is monitoring/diagnostic data.
From the tool's definition Tool name 'get_metrics_history' and description 'Get metrics history timeline (up to 60 data points at 5-second intervals)' indicate a data retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get metrics history timeline (up to 60 data points at 5-second intervals). It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for get_metrics_history: 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 Overlord MCP Server. Nothing to install.
get_metrics_history 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_metrics_history 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_metrics_history. 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_metrics_history is provided by the Overlord MCP Server MCP server (skeeminator/overlord-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 →