Retrieve AML / watchlist screening output for a workflow — sanctions hits, PEP hits, adverse-media hits with source citations and match confidence. Requires a workflow that included a screening capability.
AI agents call retrieve_screening_result 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 tool retrieves anti-money laundering (AML) and watchlist screening results for compliance purposes. It reads pre-computed screening data (sanctions, politically exposed persons, adverse media) without modifying any state. While high-sensitivity financial compliance data is accessed, the action itself is a pure retrieval with no side effects.
From the tool's definition Tool description uses 'Retrieve' and lists outputs as 'screening output', 'sanctions hits', 'PEP hits', 'adverse-media hits' — all read-only data retrieval with no modification, creation, or deletion of records.
Documented attack patterns abuse exactly the kind of access retrieve_screening_result 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 retrieve_screening_result:
{
"version": "1",
"default": "deny",
"tools": {
"retrieve_screening_result": {}
}
}retrieve_screening_result 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.
Retrieve AML / watchlist screening output for a workflow — sanctions hits, PEP hits, adverse-media hits with source citations and match confidence. Requires a workflow that included a screening capability. 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 retrieve_screening_result: 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.
retrieve_screening_result 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 retrieve_screening_result 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 retrieve_screening_result. 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.
retrieve_screening_result 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.