Low Risk

retrieve_facemap

Retrieve the biometric facemap (face template) generated during a workflow. Used for downstream face-search / re-verification flows; subject to biometric-data retention rules — handle accordingly.

How to control retrieve_facemap ↓

What retrieve_facemap does on Mcp Afip

AI agents call retrieve_facemap 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.

Low Risk

Why retrieve_facemap needs a policy

The tool performs a retrieval operation (Read category). Although biometric data is highly sensitive and its exposure poses significant privacy and security risks (justifying 'high' severity), the tool itself does not modify, delete, or execute external operations — it only queries and returns existing biometric data.

From the tool's definition Tool name 'retrieve_facemap' and description 'Retrieve the biometric facemap' — explicit retrieval action with no modification or deletion. However, the data retrieved is sensitive biometric information ('face template') subject to regulatory retention rules.

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

How to control retrieve_facemap

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_facemap:

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

retrieve_facemap 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 Afip — 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_facemap

What does the retrieve_facemap tool do? +

Retrieve the biometric facemap (face template) generated during a workflow. Used for downstream face-search / re-verification flows; subject to biometric-data retention rules — handle accordingly. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_facemap? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for retrieve_facemap: 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.

What risk level is retrieve_facemap? +

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

Can I rate-limit retrieve_facemap? +

Yes. Add a rate_limit block to the retrieve_facemap 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_facemap completely? +

Set action: deny in the PolicyLayer policy for retrieve_facemap. 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_facemap? +

retrieve_facemap 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.