Low Risk

GetLastChanges

Returns the latest changes of fundamental data. This endpoint helps consume API credits more efficiently and request new data once it is updated.

How to control GetLastChanges ↓

AI agents call GetLastChanges to retrieve information from Twelve Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves updated fundamental market data. It has no side effects—it does not create, modify, delete, or execute operations. The emphasis on consuming 'API credits more efficiently' confirms this is a read-only data retrieval endpoint.

From the tool's definition Tool name 'GetLastChanges' and description 'Returns the latest changes of fundamental data' indicates a retrieval operation. The stated purpose is to 'request new data once it is updated' without modifying or deleting any data.

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

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

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

GetLastChanges 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 Twelve Data MCP Server — 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.

Go deeper

What does the GetLastChanges tool do? +

Returns the latest changes of fundamental data. This endpoint helps consume API credits more efficiently and request new data once it is updated. It is categorised as a Read tool in the Twelve Data MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on GetLastChanges? +

Register the Twelve Data MCP Server MCP server in PolicyLayer and add a rule for GetLastChanges: 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 Twelve Data MCP Server. Nothing to install.

What risk level is GetLastChanges? +

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

Can I rate-limit GetLastChanges? +

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

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

GetLastChanges is provided by the Twelve Data MCP Server MCP server (twelvedata/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Twelve Data MCP Server tool call.

Deterministic rules across all 186 Twelve Data MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

186 Twelve Data MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.