AI agents call list_columns to retrieve information from Tick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about kanban columns within a project. It performs no creation, modification, deletion, or execution of external operations. The verb 'list' is a standard read operation that has no side effects on the system state.
From the tool's definition Tool name 'list_columns' and description 'List kanban columns for a project' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List kanban columns for a project. It is categorised as a Read tool in the Tick MCP Server, which means it retrieves data without modifying state.
Register the Tick MCP server in PolicyLayer and add a rule for list_columns: 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 Tick. Nothing to install.
list_columns 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_columns 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_columns. 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_columns is provided by the Tick MCP server (kpihx/tick-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 →