Low Risk

get_variable_history

Get the historical series for any monetary variable by id, with optional date range. Use list_variables to discover ids.

How to control get_variable_history ↓

What get_variable_history does on Mcp Ap2

AI agents call get_variable_history to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_variable_history needs a policy

This tool retrieves historical data about monetary variables within a time range. It is a read-only query operation with no side effects—it does not create, modify, delete, or execute actions. The blast radius is minimal since it only exposes historical financial data visibility without the ability to alter state or trigger transactions.

From the tool's definition Tool name 'get_variable_history' and description 'Get the historical series for any monetary variable by id' indicate data retrieval with no modification capability.

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

How to control get_variable_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_variable_history:

policy.json
{
  "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.

  1. Create a free account and register Mcp Ap2 — 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 get_variable_history

What does the get_variable_history tool do? +

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 Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_variable_history? +

Register the Mcp Ap2 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 Ap2. Nothing to install.

What risk level is get_variable_history? +

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

Can I rate-limit get_variable_history? +

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.

How do I block get_variable_history completely? +

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.

What MCP server provides get_variable_history? +

get_variable_history is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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 Ap2 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.