get_run_output
AI agents call get_run_output to retrieve information from RunWhen Platform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch or retrieve output from previously executed run sessions within the RunWhen platform. Retrieval of data with no side effects falls into the Read category. Severity is low because reading run output poses minimal risk unless the output itself contains highly sensitive data, but the tool itself performs no destructive, executable, or financial operations.
From the tool's definition Tool name 'get_run_output' indicates retrieval of output data from a run session. The description is empty, but the name and context (sibling tools include read operations like 'get_assistant') suggest this retrieves or queries existing run session data…
Attacks that exploit this kind of access
get_run_output. It is categorised as a Read tool in the RunWhen Platform MCP MCP Server, which means it retrieves data without modifying state.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for get_run_output: 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 RunWhen Platform MCP. Nothing to install.
get_run_output 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_output 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_output. 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_output is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →