Stream logs from a workflow execution with configurable log level and collection timeout. Collects logs for specified duration (default 10s), useful for monitoring workflow progress and debugging. Call repeatedly to continue collecting logs from running workflows.
AI agents call get_workflow_logs to retrieve information from Rockfish MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and streams existing log data from a workflow that is already running. It is purely observational—it reads historical log output without creating, modifying, deleting, or triggering any new operations. The configurable log level and timeout are read-side parameters. Calling it repeatedly only continues to retrieve logs, not execute new workflows or change state.
From the tool's definition Tool name 'get_workflow_logs' and description 'Stream logs from a workflow execution' with 'Collects logs for specified duration' and 'useful for monitoring workflow progress and debugging'.
Attacks that exploit this kind of access
Stream logs from a workflow execution with configurable log level and collection timeout. Collects logs for specified duration (default 10s), useful for monitoring workflow progress and debugging. Call repeatedly to continue collecting logs from running workflows. It is categorised as a Read tool in the Rockfish MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rockfish MCP Server MCP server in PolicyLayer and add a rule for 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 Rockfish MCP Server. Nothing to install.
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 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 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.
get_workflow_logs is provided by the Rockfish MCP Server MCP server (wolfdancer/rockfish-mcp). 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 →