get-run
Get details of a specific code execution run including full JSONL log
This record as markdown: /tools/io-github-portel-dev-ncp/get-run.md
What get-run does on Ncp
AI agents call get-run to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-run is rated Low
This tool retrieves historical information about a completed code execution run. It queries and returns data (JSONL logs and execution details) without executing code, modifying state, or causing side effects. The blast radius of misuse is minimal—an agent could access logs it shouldn't, but cannot alter, delete, or trigger new executions.
From the tool's definition Tool name 'get-run' and description 'Get details of a specific code execution run including full JSONL log' indicates retrieval of run information.
Attacks that exploit this kind of access
The rule that runs get-run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-run, this is the rule to start with:
get-run 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 Ncp, apply this rule, and every get-run call is checked against it from then on.
Questions about get-run
Get details of a specific code execution run including full JSONL log. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for get-run: 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 Ncp. Nothing to install.
get-run 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 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. 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 is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue