Low Risk

get_project_stats

get_project_stats

How to control get_project_stats ↓

AI agents call get_project_stats to retrieve information from Taiga MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Based on the naming pattern, this tool retrieves statistics about projects—a read operation with no side effects. The absence of mutation verbs (create, update, delete, assign) and the 'get_' prefix confirm it as a Read category tool. Low severity because statistical data retrieval poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_project_stats' indicates retrieval of project statistics. The 'get_' prefix is characteristic of read-only query operations. No description provided, but the naming convention strongly suggests data retrieval without modification.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Taiga MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_stats:

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

get_project_stats 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 Taiga MCP Bridge — 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.

Go deeper

What does the get_project_stats tool do? +

get_project_stats. It is categorised as a Read tool in the Taiga MCP Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_stats? +

Register the Taiga MCP Bridge 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 Taiga MCP Bridge. Nothing to install.

What risk level is get_project_stats? +

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

Can I rate-limit get_project_stats? +

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.

How do I block get_project_stats completely? +

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.

What MCP server provides get_project_stats? +

get_project_stats is provided by the Taiga MCP Bridge MCP server (talhaorak/pytaiga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Taiga MCP Bridge tool call.

Deterministic rules across all 94 Taiga MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

94 Taiga MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ 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.