gluecron_get_workflow_run
Fetch a workflow run's metadata + status. Mirrors GET /api/v2/repos/.../actions/runs/:id.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-get-workflow-run.md
What gluecron_get_workflow_run does on Gluecron
AI agents call gluecron_get_workflow_run to retrieve information from Gluecron 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 |
|---|---|---|---|
repo | string | Yes | |
owner | string | Yes | |
run_id | string | Yes |
Parameters from the server's own tool schema.
Why gluecron_get_workflow_run is rated Low
This tool retrieves workflow run information via a GET API endpoint. It has no side effects—it only queries and returns metadata and status information about an existing workflow run. This is a pure read operation with minimal blast radius if misused by an AI agent (at worst, information disclosure of workflow details the agent may not be authorized to see, but no data modification or execution).
From the tool's definition Tool name and description indicate fetching/retrieving data: 'Fetch a workflow run's metadata + status' and 'Mirrors GET'. No modification, deletion, or execution of code is described.
Attacks that exploit this kind of access
The rule that runs gluecron_get_workflow_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_get_workflow_run, this is the rule to start with:
gluecron_get_workflow_run 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 Gluecron, apply this rule, and every gluecron_get_workflow_run call is checked against it from then on.
Questions about gluecron_get_workflow_run
Fetch a workflow run's metadata + status. Mirrors GET /api/v2/repos/.../actions/runs/:id. It is categorised as a Read tool in the Gluecron MCP Server, which means it retrieves data without modifying state.
gluecron_get_workflow_run accepts 3 parameters: repo, owner, run_id. Required: repo, owner, run_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_get_workflow_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 Gluecron. Nothing to install.
gluecron_get_workflow_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 gluecron_get_workflow_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 gluecron_get_workflow_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.
gluecron_get_workflow_run is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
This server
Across the catalogue