Low Risk

properties_lookup

Real-estate lookup by address or registration — property type, area, owner history, market value estimate. POST /v1/datasets/properties.

How to control properties_lookup ↓

What properties_lookup does on Mcp Afip

AI agents call properties_lookup 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 properties_lookup needs a policy

This tool queries and retrieves publicly-accessible or government-registered property data without modifying, deleting, or committing financial obligations. It is a read-only data retrieval operation with no side effects beyond returning information. Severity is low because property lookup data is typically non-sensitive in a tax authority context and provides no direct harm vector.

From the tool's definition Tool description states 'lookup' and retrieves property information: 'property type, area, owner history, market value estimate.' The POST method is used for querying, not mutation. No modification, deletion, or financial transaction occurs.

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

How to control properties_lookup

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

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

properties_lookup 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 properties_lookup

What does the properties_lookup tool do? +

Real-estate lookup by address or registration — property type, area, owner history, market value estimate. POST /v1/datasets/properties. 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 properties_lookup? +

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

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

Can I rate-limit properties_lookup? +

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

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

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