Get aggregated statistics for a project: total issues, open vs closed, and breakdowns by status, priority, and type. e.g., project:
AI agents call get_project_stats to retrieve information from Issue Tracker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_project_stats is a pure data retrieval operation that queries and returns analytics information about a project. It produces no side effects, creates no new data, executes no external commands, and does not modify or delete existing records. The only risk is information disclosure, which is inherent to read operations and typically low severity in most contexts.
From the tool's definition Tool retrieves aggregated statistics (total issues, open vs closed, breakdowns by status, priority, and type) with no modification or deletion capability. The description indicates data retrieval only: 'Get aggregated statistics for a project'.
Attacks that exploit this kind of access
Get aggregated statistics for a project: total issues, open vs closed, and breakdowns by status, priority, and type. e.g., project:. It is categorised as a Read tool in the Issue Tracker MCP MCP Server, which means it retrieves data without modifying state.
Register the Issue Tracker 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 Issue Tracker MCP. 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 Issue Tracker MCP server (josephtandle/jira-mcp-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 →