shortcut_search_stories
Search Shortcut stories with the search syntax.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/shortcut-search-stories.md
What shortcut_search_stories does on UnClick
AI agents call shortcut_search_stories 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 |
|---|---|---|---|
limit | number | — | Results to return (max 25, default 25) |
query | string | Yes | Search query (e.g. 'state:"In Progress" owner:me') |
api_token | string | Yes | Shortcut API token |
Parameters from the server's own tool schema.
Why shortcut_search_stories is rated Low
The tool retrieves or queries stories from a Shortcut system based on search parameters. No data is created, modified, deleted, or executed. This is a standard read/retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'search' and description states 'Search Shortcut stories with the search syntax.' This is a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs shortcut_search_stories 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 shortcut_search_stories, this is the rule to start with:
shortcut_search_stories 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 shortcut_search_stories call is checked against it from then on.
Questions about shortcut_search_stories
Search Shortcut stories with the search syntax. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
shortcut_search_stories accepts 3 parameters: limit, query, api_token. Required: query, api_token. 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 shortcut_search_stories: 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.
shortcut_search_stories 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 shortcut_search_stories 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 shortcut_search_stories. 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.
shortcut_search_stories 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