AI agents call get_run_info to retrieve information from Mcp Dagster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves detailed information about a specific run in Dagster, which is a read-only operation with no side effects. It queries existing data about run status, logs, and metadata but does not create, modify, delete, or execute any operations. The low severity reflects minimal blast radius—an AI agent misusing this tool would only see information it shouldn't have access to, not cause operational damage.
From the tool's definition Tool name 'get_run_info' and description 'Get detailed information about a specific run' indicate a query operation that retrieves data about a Dagster run without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_run_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Dagster, and nothing reaches the server without passing your rules. This is the rule we recommend for get_run_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_run_info": {}
}
}get_run_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific run. It is categorised as a Read tool in the Mcp Dagster MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dagster MCP server in PolicyLayer and add a rule for get_run_info: 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 Mcp Dagster. Nothing to install.
get_run_info 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_info 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_info. 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_info is provided by the Mcp Dagster MCP server (kyryl-opens-ml/mcp-server-dagster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Dagster, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Mcp Dagster tools catalogued and risk-classified — across an index of 43,000+ MCP servers.