list_project_updates
List all updates for a specific project, showing progress history and status changes
This record as markdown: /tools/0xikarus-linear-kanban-mcp/list-project-updates.md
What list_project_updates does on Linear Kanban Server
AI agents call list_project_updates to retrieve information from Linear Kanban Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_project_updates is rated Low
This tool queries and retrieves historical project update data without creating, modifying, or deleting any information. It is a straightforward read operation that returns existing project progress information. The blast radius of misuse is minimal—an agent querying project updates poses no risk of data loss, unauthorized changes, or side effects beyond information disclosure.
From the tool's definition Tool name 'list_project_updates' and description 'List all updates for a specific project, showing progress history and status changes' indicate data retrieval with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs list_project_updates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear Kanban Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_project_updates, this is the rule to start with:
list_project_updates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear Kanban Server, apply this rule, and every list_project_updates call is checked against it from then on.
Questions about list_project_updates
List all updates for a specific project, showing progress history and status changes. It is categorised as a Read tool in the Linear Kanban Server MCP Server, which means it retrieves data without modifying state.
Register the Linear Kanban Server MCP server in PolicyLayer and add a rule for list_project_updates: 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 Linear Kanban Server. Nothing to install.
list_project_updates 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_project_updates 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_project_updates. 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_project_updates is provided by the Linear Kanban Server MCP server (0xikarus/linear-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear Kanban Server, and thousands of servers like it.
This server
Across the catalogue