AI agents call get_run to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes | The run_id returned by start_crew_run |
Parameters from the server's own tool schema.
This tool retrieves status information about a prior execution (a 'Crews run'). It queries data and returns a summary card. There is no creation, modification, deletion, or execution of new operations—merely inspection of existing run state. This is a classic Read operation with minimal security risk.
From the tool's definition Tool description states it 'Returns a ConversationalCard summarising stage progress, token usage, and any failure artifact.' The verb 'Returns' and the read-only nature of retrieving status information indicate this is a query operation with no side effects.
Attacks that exploit this kind of access
Call this tool when the user wants the status of a specific Crews run. Returns a ConversationalCard summarising stage progress, token usage, and any failure artifact. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_run accepts 1 parameter: run_id. Required: run_id. 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 get_run: 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.
get_run 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 get_run 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 get_run. 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.
get_run 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →