Get overall statistics about all projects and tasks
AI agents call get_project_stats to retrieve information from Project Tracking 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 aggregated statistics (counts, summaries) from the project database without creating, modifying, or deleting any data. It is a read-only query operation with no side effects, placing it firmly in the Read category. Severity is low because misuse (e.g., an agent repeatedly calling it) would only cause minor resource consumption with no data loss or unauthorized state changes.
From the tool's definition Tool name 'get_project_stats' and description 'Get overall statistics about all projects and tasks' indicate a retrieval operation. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
Get overall statistics about all projects and tasks. It is categorised as a Read tool in the Project Tracking MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Project Tracking MCP Server MCP server in PolicyLayer and add a rule for get_project_stats: 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 Project Tracking MCP Server. Nothing to install.
get_project_stats 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_project_stats 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_project_stats. 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_project_stats is provided by the Project Tracking MCP Server MCP server (leonj1/project-tracking-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 →