AI agents call view-project to retrieve information from Linear MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries project data with no apparent side effects. It aligns with other non-destructive query operations on the server. No creation, modification, deletion, or execution of external commands is implied. Confidence is slightly reduced due to empty description, but the naming pattern and server context provide sufficient evidence.
From the tool's definition Tool name 'view-project' indicates data retrieval. Server context shows tools like 'list-initiatives', 'list-projects', and 'search-issues' are Read operations; 'view-project' follows the same retrieval pattern.
Documented attack patterns abuse exactly the kind of access view-project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linear MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for view-project:
{
"version": "1",
"default": "deny",
"tools": {
"view-project": {}
}
}view-project 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.
view-project. It is categorised as a Read tool in the Linear MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for view-project: 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 MCP Server. Nothing to install.
view-project 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 view-project 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 view-project. 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.
view-project is provided by the Linear MCP Server MCP server (samcfinan/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linear MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Linear MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.