This record as markdown: /tools/io-github-portel-dev-ncp/executions.md
What executions does on Ncp
AI agents call executions 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 executions is rated Low
This tool retrieves and displays execution history records, which is a data query operation with no side effects. It falls clearly into the Read category as it only fetches information without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could only gain visibility into historical execution data, posing no direct risk to systems or data integrity.
From the tool's definition The tool name 'executions' combined with the description 'View execution history' indicates a read-only operation that retrieves historical data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs executions 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 executions, this is the rule to start with:
executions 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 executions call is checked against it from then on.
Questions about executions
View execution history. 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 executions: 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.
executions 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 executions 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 executions. 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.
executions 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