search_typed_links
Searches stored graph-style links extracted from Memory facts and conversation turns. Use this when a worker needs to find connections between people, jobs, PRs, receipts, files, tools, and decisions. Prefer search_memory for broad recall and search_typed_links for relationship lookups.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/search-typed-links.md
What search_typed_links does on UnClick
AI agents call search_typed_links to retrieve information from UnClick 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 |
|---|---|---|---|
query | string | Yes | Link search query |
max_results | number | — |
Parameters from the server's own tool schema.
Why search_typed_links is rated Low
This tool retrieves relational data from a stored graph structure. It performs no writes, deletes, executions, or financial operations. The worst case is unauthorized access to relationship metadata, which is a confidentiality concern rather than integrity or availability risk. Low severity due to limited blast radius from misuse.
From the tool's definition Tool description states it 'Searches stored graph-style links' and is used to 'find connections' - these are query/retrieval operations with no modification capability.
Attacks that exploit this kind of access
The rule that runs search_typed_links safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_typed_links, this is the rule to start with:
search_typed_links 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 UnClick, apply this rule, and every search_typed_links call is checked against it from then on.
Questions about search_typed_links
Searches stored graph-style links extracted from Memory facts and conversation turns. Use this when a worker needs to find connections between people, jobs, PRs, receipts, files, tools, and decisions. Prefer search_memory for broad recall and search_typed_links for relationship lookups. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
search_typed_links accepts 2 parameters: query, max_results. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for search_typed_links: 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 UnClick. Nothing to install.
search_typed_links 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_typed_links 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_typed_links. 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_typed_links is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue