search_documentation
Search Linear's documentation to learn about features and usage
This record as markdown: /tools/linear/search-documentation.md
What search_documentation does on Linear
AI agents call search_documentation to retrieve information from Linear without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | The page number |
query | string | — | The search query |
Parameters from the server's own tool schema.
Why search_documentation is rated Low
This tool retrieves information from Linear's documentation without modifying any data or triggering external operations. It is a search/query function with no side effects, fitting the Read category. Severity is low because misuse would only expose documentation already intended to be publicly available, with no blast radius.
From the tool's definition Tool name 'search_documentation' and description 'Search Linear's documentation to learn about features and usage' indicate a read-only operation that queries documentation.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_documentation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_documentation, this is the rule to start with:
search_documentation 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, apply this rule, and every search_documentation call is checked against it from then on.
Questions about search_documentation
Search Linear's documentation to learn about features and usage. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
search_documentation accepts 2 parameters: page, query. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for search_documentation: 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. Nothing to install.
search_documentation 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 search_documentation 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 search_documentation. 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.
search_documentation is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue