Access historical performance data for industries using the Historical Industry Performance API. Track long-term trends and analyze how different industries have evolved over time across various stock exchanges.
AI agents call getHistoricalIndustryPerformance to retrieve information from Financial Modeling Prep MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical industry performance metrics and trends. It has no capability to modify, delete, execute code, move money, or trigger external side effects. The blast radius of misuse is minimal—an AI agent could at worst retrieve unnecessary data or make poor analytical decisions based on the data, but cannot cause financial loss, data destruction, or unauthorized system operations.
From the tool's definition Tool name 'getHistoricalIndustryPerformance' and description 'Access historical performance data' and 'Track long-term trends and analyze' indicate data retrieval without modification.
Attacks that exploit this kind of access
Access historical performance data for industries using the Historical Industry Performance API. Track long-term trends and analyze how different industries have evolved over time across various stock exchanges. It is categorised as a Read tool in the Financial Modeling Prep MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Financial Modeling Prep MCP Server MCP server in PolicyLayer and add a rule for getHistoricalIndustryPerformance: 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 Financial Modeling Prep MCP Server. Nothing to install.
getHistoricalIndustryPerformance 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 getHistoricalIndustryPerformance 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 getHistoricalIndustryPerformance. 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.
getHistoricalIndustryPerformance is provided by the Financial Modeling Prep MCP Server MCP server (vijitdaroch/financial-modeling-prep-mcp-server). 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 →