Low Risk

get_tag_statistics

Get statistics for all tags. Returns: Tag statistics including task counts per tag

How to control get_tag_statistics ↓

What get_tag_statistics does on Taskdog

AI agents call get_tag_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.

Low Risk

Why get_tag_statistics needs a policy

This tool retrieves and queries aggregate statistics about tags without creating, modifying, deleting, or executing any operations. It has no side effects and is purely informational. The blast radius of misuse is minimal—an agent could at worst retrieve statistical data it shouldn't see, which is a low-severity information disclosure risk.

From the tool's definition Tool name 'get_tag_statistics' and description 'Get statistics for all tags' with 'Returns: Tag statistics including task counts per tag' indicate a pure retrieval operation with no modification, deletion, or execution of external commands.

Documented attack patterns abuse exactly the kind of access get_tag_statistics gives an agent:

How to control get_tag_statistics

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_tag_statistics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tag_statistics": {}
  }
}

get_tag_statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Taskdog — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_tag_statistics

What does the get_tag_statistics tool do? +

Get statistics for all tags. Returns: Tag statistics including task counts per tag. It is categorised as a Read tool in the Taskdog MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag_statistics? +

Register the Taskdog MCP server in PolicyLayer and add a rule for get_tag_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.

What risk level is get_tag_statistics? +

get_tag_statistics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tag_statistics? +

Yes. Add a rate_limit block to the get_tag_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.

How do I block get_tag_statistics completely? +

Set action: deny in the PolicyLayer policy for get_tag_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.

What MCP server provides get_tag_statistics? +

get_tag_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.

Enforce policy on every Taskdog tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.