New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_run

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.

SERVERUnClick SOURCE@unclick/mcp-server
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/get-run.md

What get_run does on UnClick

AI agents call get_run 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.

ParameterTypeRequiredDescription
run_id string Yes The run_id returned by start_crew_run

Parameters from the server's own tool schema.

Why get_run is rated Low

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.

Questions about get_run

What does the get_run tool do? +

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.

What parameters does get_run accept? +

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.

How do I enforce a policy on get_run? +

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.

What risk level is get_run? +

get_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_run? +

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.

How do I block get_run completely? +

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.

What MCP server provides get_run? +

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.

More on UnClick, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.