Get heatmap data showing event density for each day of a year
AI agents call yaag_get_heatmap to retrieve information from YearAtAGlance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays aggregated calendar statistics (event density heatmap data). It does not create, modify, delete, execute code, or trigger external operations. It is a straightforward data retrieval function with no capability to alter system state or user data.
From the tool's definition Tool name is 'yaag_get_heatmap' and description states it retrieves ('Get') heatmap data showing event density—a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get heatmap data showing event density for each day of a year. It is categorised as a Read tool in the YearAtAGlance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YearAtAGlance MCP Server MCP server in PolicyLayer and add a rule for yaag_get_heatmap: 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 YearAtAGlance MCP Server. Nothing to install.
yaag_get_heatmap 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 yaag_get_heatmap 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 yaag_get_heatmap. 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.
yaag_get_heatmap is provided by the YearAtAGlance MCP Server MCP server (mindfullabai/yearataglance-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 →