Get aggregated metrics summary for a time period
AI agents call get_daily_summary to retrieve information from Climux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical metrics data for reporting purposes. It has no capability to modify state, execute operations, delete data, or trigger external actions. The blast radius of misuse is minimal—an agent could only access summary information that is already logged or computed, with no destructive or operational consequences.
From the tool's definition Tool name 'get_daily_summary' and description 'Get aggregated metrics summary for a time period' indicate data retrieval with no modification or side effects. The verb 'Get' and the plural noun 'metrics summary' are consistent with a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_daily_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Climux, and nothing reaches the server without passing your rules. This is the rule we recommend for get_daily_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_daily_summary": {}
}
}get_daily_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 aggregated metrics summary for a time period. It is categorised as a Read tool in the Climux MCP Server, which means it retrieves data without modifying state.
Register the Climux MCP server in PolicyLayer and add a rule for get_daily_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 Climux. Nothing to install.
get_daily_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_daily_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_daily_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_daily_summary is provided by the Climux MCP server (veithly/climux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Climux, 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.
9 Climux tools catalogued and risk-classified — across an index of 43,000+ MCP servers.