This record as markdown: /tools/io-github-nograai-nogra-mcp/recent-runs.md
What recent_runs does on Nogra
AI agents call recent_runs to retrieve information from Nogra without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why recent_runs is rated Low
The name indicates a retrieval operation that queries or lists recent runs/executions. With an empty description, there is uncertainty, but 'recent_runs' most naturally maps to a read operation that returns data about past activity without modifying or executing anything.
From the tool's definition Tool name 'recent_runs' suggests querying historical execution records with no parameters or side effects described.
Attacks that exploit this kind of access
The rule that runs recent_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nogra, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recent_runs, this is the rule to start with:
recent_runs 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 Nogra, apply this rule, and every recent_runs call is checked against it from then on.
Questions about recent_runs
recent_runs is a read tool on the Nogra MCP server. It is categorised as a Read tool in the Nogra MCP Server, which means it retrieves data without modifying state.
Register the Nogra MCP server in PolicyLayer and add a rule for recent_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 Nogra. Nothing to install.
recent_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 recent_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 recent_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.
recent_runs is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nogra, and thousands of servers like it.
This server
Across the catalogue