Fetch the status of a Sift Workflow run (GET /v3/accounts/{account_id}/workflows/runs/{run_id}). The run_id is returned in the response to events sent with return_workflow_status=true. The run status tells you which route of the workflow was taken and which decisions were applied. Requires SIFT_A...
AI agents call get_workflow_run to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query operation that retrieves read-only workflow execution status from the AFIP system. The GET HTTP method and 'Fetch' verb confirm retrieval semantics. While it operates within a tax authority context, accessing workflow run metadata poses minimal security risk — it neither executes transactions, deletes data, nor modifies financial records.
From the tool's definition Tool name 'get_workflow_run' and description uses 'Fetch' and 'GET' — retrieves workflow run status without modification. Returns run status and routing information. No state changes, no side effects.
Documented attack patterns abuse exactly the kind of access get_workflow_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workflow_run:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_run": {}
}
}get_workflow_run 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.
Fetch the status of a Sift Workflow run (GET /v3/accounts/{account_id}/workflows/runs/{run_id}). The run_id is returned in the response to events sent with return_workflow_status=true. The run status tells you which route of the workflow was taken and which decisions were applied. Requires SIFT_ACCOUNT_ID. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for get_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 Afip. Nothing to install.
get_workflow_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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_workflow_run is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.