Check whether a cheque has been reported as stolen/lost (denunciado) by entity code and cheque number
AI agents call validate_cheque 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 the status of a cheque (whether it has been reported as stolen/lost) from the AFIP database. It is a read-only query that returns existing information without creating, modifying, or deleting data. The blast radius of misuse is minimal—worst case, an agent could make repeated validation queries, but this poses no financial risk, data integrity risk, or operational harm.
From the tool's definition Tool name 'validate_cheque' and description 'Check whether a cheque has been reported as stolen/lost' indicates a query/lookup operation with no data modification or irreversible action.
Documented attack patterns abuse exactly the kind of access validate_cheque 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 validate_cheque:
{
"version": "1",
"default": "deny",
"tools": {
"validate_cheque": {}
}
} validate_cheque 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.
Check whether a cheque has been reported as stolen/lost (denunciado) by entity code and cheque number. 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 validate_cheque: 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.
validate_cheque 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 validate_cheque 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 validate_cheque. 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.
validate_cheque 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.