This API endpoint returns a breakdown of the estimated historical EPS changes at a given period.
AI agents call GetEpsTrend 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.
GetEpsTrend retrieves and queries historical earnings per share (EPS) trend data from the Twelve Data API. This is a passive read operation with no side effects, no code execution, no data modification, and no financial transactions. Even though the server provides financial market data, this specific tool only reads/retrieves information rather than executing trades, making payments, or modifying records.
From the tool's definition Tool returns 'a breakdown of the estimated historical EPS changes' - purely a data retrieval function that queries financial metrics without modifying, executing operations, or affecting financial transactions.
Documented attack patterns abuse exactly the kind of access GetEpsTrend 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 GetEpsTrend:
{
"version": "1",
"default": "deny",
"tools": {
"GetEpsTrend": {}
}
}GetEpsTrend 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.
This API endpoint returns a breakdown of the estimated historical EPS changes at a given period. It is categorised as a Read tool in the Twelve Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twelve Data MCP Server MCP server in PolicyLayer and add a rule for GetEpsTrend: 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.
GetEpsTrend 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 GetEpsTrend 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 GetEpsTrend. 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.
GetEpsTrend 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.
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.