AI agents call get_issue_by_ref 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.
The tool retrieves data about an issue without modifying, deleting, or executing operations. This is a standard read operation typical of project management systems. The empty description slightly reduces confidence, but the clear 'get_' prefix and sibling tools that explicitly perform write/create operations (create_epic, add_comment, assign_*) confirm this tool's read-only nature.
From the tool's definition Tool name 'get_issue_by_ref' indicates retrieval of an issue by reference identifier; no description provided, but naming convention and context within a project management platform suggest read-only query operation.
Documented attack patterns abuse exactly the kind of access get_issue_by_ref 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_issue_by_ref:
{
"version": "1",
"default": "deny",
"tools": {
"get_issue_by_ref": {}
}
}get_issue_by_ref is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_issue_by_ref. It is categorised as a Read tool in the Taiga MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Taiga MCP Bridge MCP server in PolicyLayer and add a rule for get_issue_by_ref: 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.
get_issue_by_ref 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_issue_by_ref 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_issue_by_ref. 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_issue_by_ref 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.
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.