Get last elements for a specific date (YYMMDD format)
AI agents call get_last_elements_by_date to retrieve information from AI Prediction MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation that queries trading prediction data by date. It has no capability to modify, delete, execute code, or move funds. The tool is passive data access only, making it a Read category risk with low severity.
From the tool's definition Tool description states 'Get last elements for a specific date' and name indicates retrieval ('get_last_elements'). No modification, deletion, or execution of code indicated. Returns data from aiprediction.us API without side effects.
Attacks that exploit this kind of access
Get last elements for a specific date (YYMMDD format). It is categorised as a Read tool in the AI Prediction MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AI Prediction MCP Server MCP server in PolicyLayer and add a rule for get_last_elements_by_date: 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 AI Prediction MCP Server. Nothing to install.
get_last_elements_by_date 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_last_elements_by_date 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_last_elements_by_date. 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_last_elements_by_date is provided by the AI Prediction MCP Server MCP server (phsphd/mcpserver_aiprediction_us). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →