Get the execution history for a specific pipeline. Shows all runs with their status, duration, and results.
AI agents call binelek_get_pipeline_runs to retrieve information from Binelek 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 displays historical data about pipeline execution (status, duration, results). It performs a query operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is limited to information disclosure of pipeline metadata.
From the tool's definition Tool description states 'Get the execution history for a specific pipeline. Shows all runs with their status, duration, and results.' The verb 'Get' and 'Shows' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get the execution history for a specific pipeline. Shows all runs with their status, duration, and results. It is categorised as a Read tool in the Binelek MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binelek MCP Server MCP server in PolicyLayer and add a rule for binelek_get_pipeline_runs: 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 Binelek MCP Server. Nothing to install.
binelek_get_pipeline_runs 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 binelek_get_pipeline_runs 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 binelek_get_pipeline_runs. 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.
binelek_get_pipeline_runs is provided by the Binelek MCP Server MCP server (k5tuck/binelek-mcp-server). 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 →