Get the historical series for any monetary variable by id, with optional date range. Use list_variables to discover ids.
AI agents call get_variable_history 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 historical monetary data (such as exchange rates, tax coefficients, or inflation indices maintained by AFIP) based on variable IDs and optional date ranges. It performs pure data retrieval with no side effects, no code execution, and no state changes. While the data may be sensitive in a financial context, the tool itself cannot modify records, execute operations, or create financial obligations.
From the tool's definition Tool name 'get_variable_history' and description 'Get the historical series for any monetary variable by id' indicate retrieval of historical data.
Documented attack patterns abuse exactly the kind of access get_variable_history 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_variable_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_variable_history": {}
}
} get_variable_history 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 the historical series for any monetary variable by id, with optional date range. Use list_variables to discover ids. 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_variable_history: 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_variable_history 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_variable_history 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_variable_history. 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_variable_history 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.