gluecron_get_workflow_logs
Return concatenated per-job logs for a workflow run, plus per-job metadata. JSON-friendly companion to the ZIP-download endpoint.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-get-workflow-logs.md
What gluecron_get_workflow_logs does on Gluecron
AI agents call gluecron_get_workflow_logs 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_logs is rated Low
This is a read-only operation that queries and retrieves logs and metadata from an existing workflow run. It has no capability to modify, execute, delete, or trigger any external operations. The blast radius of misuse is minimal — an agent could only access logs it already has authorization to view, with no destructive or unintended consequences possible.
From the tool's definition Tool returns (reads) workflow logs and metadata without modifying, creating, or deleting any data. The description states it 'Return[s] concatenated per-job logs' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs gluecron_get_workflow_logs 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_logs, this is the rule to start with:
gluecron_get_workflow_logs 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_logs call is checked against it from then on.
Questions about gluecron_get_workflow_logs
Return concatenated per-job logs for a workflow run, plus per-job metadata. JSON-friendly companion to the ZIP-download endpoint. It is categorised as a Read tool in the Gluecron MCP Server, which means it retrieves data without modifying state.
gluecron_get_workflow_logs 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_logs: 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_logs 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_logs 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_logs. 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_logs 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