Get summary of tasks for a time period (today, week, month)
AI agents call get_summary to retrieve information from Productivity Tracker 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 and presents task data for specific time periods without creating, modifying, or deleting any information. It has no side effects on the underlying database beyond querying. The blast radius of misuse is minimal—an AI agent could only over-query or access summaries, posing no risk to data integrity or financial operations.
From the tool's definition Tool name 'get_summary' and description 'Get summary of tasks for a time period' indicates retrieval and aggregation of existing data with no modification or deletion. The verb 'get' and 'summary' are characteristic of read operations.
Attacks that exploit this kind of access
Get summary of tasks for a time period (today, week, month). It is categorised as a Read tool in the Productivity Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Productivity Tracker MCP Server MCP server in PolicyLayer and add a rule for get_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 Productivity Tracker MCP Server. Nothing to install.
get_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_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_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_summary is provided by the Productivity Tracker MCP Server MCP server (manasamadgul/tracker). 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 →