Low Risk

list_points

list_points

How to control list_points ↓

AI agents call list_points 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

Despite the empty description reducing confidence slightly, the 'list_' prefix is a strong indicator of a Read operation that retrieves or queries data from Taiga without modification. This aligns with standard project management tool behavior where listing points is a non-destructive information retrieval task. Low severity due to no capability to modify, delete, or execute actions.

From the tool's definition Tool name 'list_points' indicates a query/retrieval operation. The verb 'list' is characteristic of Read operations that fetch data without side effects.

Documented attack patterns abuse exactly the kind of access list_points 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 list_points:

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

list_points 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 list_points tool do? +

list_points. 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 list_points? +

Register the Taiga MCP Bridge MCP server in PolicyLayer and add a rule for list_points: 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 list_points? +

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

Can I rate-limit list_points? +

Yes. Add a rate_limit block to the list_points 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 list_points completely? +

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

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