Get task statistics. Args: period: Time period for statistics (all, 7d, 30d) Returns: Statistics including counts by status, completion rates, etc.
AI agents call get_statistics to retrieve information from Taskdog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries statistical data about tasks (counts, completion rates) without creating, modifying, deleting, or executing any operations. It is a pure read operation with no destructive, financial, or execution implications. The time period parameter only filters which data to retrieve, not what actions to perform.
From the tool's definition Tool name is 'get_statistics' and description states it 'Get[s] task statistics' and 'Returns: Statistics including counts by status, completion rates, etc.' The verb 'get' and the read-only return of aggregated statistics indicate no side effects or data…
Documented attack patterns abuse exactly the kind of access get_statistics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. This is the rule we recommend for get_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get_statistics": {}
}
} get_statistics 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 task statistics. Args: period: Time period for statistics (all, 7d, 30d) Returns: Statistics including counts by status, completion rates, etc. It is categorised as a Read tool in the Taskdog MCP Server, which means it retrieves data without modifying state.
Register the Taskdog MCP server in PolicyLayer and add a rule for get_statistics: 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 Taskdog. Nothing to install.
get_statistics 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_statistics 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_statistics. 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_statistics is provided by the Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taskdog, 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.
26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.