Verify a Verifiable Credential (intent, cart, or payment mandate). Checks signature, issuer trust, expiry, and revocation status.
AI agents call verify_credential 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.
The tool only validates and inspects credential properties (signature, issuer, expiry, revocation status) without modifying state, executing external code, or causing financial transactions. It is purely informational/verification in nature, making it a Read category risk with low severity.
From the tool's definition Tool performs verification checks on existing credentials: 'Checks signature, issuer trust, expiry, and revocation status.' These are read-only validation operations with no data modification, creation, or deletion.
Documented attack patterns abuse exactly the kind of access verify_credential 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 verify_credential:
{
"version": "1",
"default": "deny",
"tools": {
"verify_credential": {}
}
} verify_credential 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.
Verify a Verifiable Credential (intent, cart, or payment mandate). Checks signature, issuer trust, expiry, and revocation status. 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 verify_credential: 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.
verify_credential 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 verify_credential 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 verify_credential. 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.
verify_credential 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.