Get metadata (name, WhatsApp display name, profile picture, status) for a single contact
AI agents call get_contact_metadata 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 only queries and returns contact information with no side effects, modifications, or state changes. The metadata retrieved (name, display name, profile picture, status) are informational attributes. The blast radius of misuse is low—an AI agent could enumerate contacts or gather contact details, but cannot modify data, execute operations, or cause financial or destructive harm.
From the tool's definition The tool retrieves metadata (name, WhatsApp display name, profile picture, status) for a single contact. The verb 'get' and the nature of metadata retrieval—extracting information without modification—clearly indicate a read-only operation.
Documented attack patterns abuse exactly the kind of access get_contact_metadata 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_contact_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_contact_metadata": {}
}
} get_contact_metadata 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.
Get metadata (name, WhatsApp display name, profile picture, status) for a single contact. 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_contact_metadata: 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_contact_metadata 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_contact_metadata 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_contact_metadata. 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_contact_metadata 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.