AI agents call list_custom_attributes 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 'list_' prefix strongly suggests a read-only retrieval operation that queries and returns custom attributes from the Taiga project management platform without modifying any data. No side effects or reversible changes occur. While the description is empty, the naming convention is unambiguous and consistent with standard API design patterns where 'list' operations are read-only.
From the tool's definition Tool name 'list_custom_attributes' with 'list' prefix indicates data retrieval operation; sibling tools on this server follow clear patterns where 'create_*', 'assign_*', 'bulk_create_*', 'bulk_update_*' modify data, while this tool queries/lists existing…
Documented attack patterns abuse exactly the kind of access list_custom_attributes 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_custom_attributes:
{
"version": "1",
"default": "deny",
"tools": {
"list_custom_attributes": {}
}
}list_custom_attributes 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.
list_custom_attributes. 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 list_custom_attributes: 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.
list_custom_attributes 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 list_custom_attributes 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 list_custom_attributes. 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.
list_custom_attributes 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.