Access historical employee count data for a company based on specific reporting periods. The FMP Company Historical Employee Count API provides insights into how a company’s workforce has evolved over time, allowing users to analyze growth trends and operational changes.
AI agents call getHistoricalEmployeeCount 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 historical workforce data from a company's reporting periods. It is a read-only query operation that returns informational data about past employee counts. There are no side effects, no data modification, no code execution, and no financial transactions involved. The blast radius of misuse is minimal — an AI agent could only return incorrect or stale information to a user.
From the tool's definition Tool name is 'getHistoricalEmployeeCount' and description states it 'provides insights into how a company's workforce has evolved over time' — purely data retrieval with no modification, deletion, execution, or financial impact.
Attacks that exploit this kind of access
Access historical employee count data for a company based on specific reporting periods. The FMP Company Historical Employee Count API provides insights into how a company’s workforce has evolved over time, allowing users to analyze growth trends and operational changes. 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 getHistoricalEmployeeCount: 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.
getHistoricalEmployeeCount 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 getHistoricalEmployeeCount 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 getHistoricalEmployeeCount. 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.
getHistoricalEmployeeCount 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 →