Low Risk

retrieve_workflow_run

Retrieve a workflow run by id. Returns status (

How to control retrieve_workflow_run ↓

What retrieve_workflow_run does on Mcp Ap2

AI agents call retrieve_workflow_run to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why retrieve_workflow_run needs a policy

This tool performs a read-only operation—retrieving and returning workflow run information by identifier. It has no side effects on data or systems. Despite the financial context of the AP2 server, this specific tool is purely informational (Read category). Severity is low because unauthorized retrieval of workflow metadata has limited blast radius compared to tools that modify payments or trigger disputes.

From the tool's definition Tool name 'retrieve_workflow_run' and description 'Retrieve a workflow run by id. Returns status' indicate a query/fetch operation that retrieves existing data without modification.

Documented attack patterns abuse exactly the kind of access retrieve_workflow_run gives an agent:

How to control retrieve_workflow_run

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for retrieve_workflow_run:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "retrieve_workflow_run": {}
  }
}

retrieve_workflow_run is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about retrieve_workflow_run

What does the retrieve_workflow_run tool do? +

Retrieve a workflow run by id. Returns status (. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_workflow_run? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for retrieve_workflow_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 Mcp Ap2. Nothing to install.

What risk level is retrieve_workflow_run? +

retrieve_workflow_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit retrieve_workflow_run? +

Yes. Add a rate_limit block to the retrieve_workflow_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.

How do I block retrieve_workflow_run completely? +

Set action: deny in the PolicyLayer policy for retrieve_workflow_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.

What MCP server provides retrieve_workflow_run? +

retrieve_workflow_run is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.