This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/shortcut-get-story.md
What shortcut_get_story does on UnClick
AI agents call shortcut_get_story 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 |
|---|---|---|---|
story_id | string | Yes | Shortcut story id |
api_token | string | Yes | Shortcut API token |
Parameters from the server's own tool schema.
Why shortcut_get_story is rated Low
This tool retrieves data from the Shortcut project management system by ID. It has no side effects—it only queries and returns a story record. This is a straightforward read operation with minimal blast radius if misused by an AI agent, as it can only expose existing data within the Shortcut workspace.
From the tool's definition Tool name 'shortcut_get_story' with verb 'get' and description 'Get a single Shortcut story by id' indicates a retrieval operation. No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
The rule that runs shortcut_get_story 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_get_story, this is the rule to start with:
shortcut_get_story 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_get_story call is checked against it from then on.
Questions about shortcut_get_story
Get a single Shortcut story by id. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
shortcut_get_story accepts 2 parameters: story_id, api_token. Required: story_id, 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_get_story: 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_get_story 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_get_story 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_get_story. 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_get_story 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