get_company_history
Retrieve entitled Entity topic history Returns retained canonical topic history for an entitled Entity, including history older than a Watch; unentitled access returns 404. HTTP: GET /v1/entities/{domain}/history/{topic}
This record as markdown: /tools/com-replynodes-mcp/get-company-history.md
What get_company_history does on ReplyNodes
AI agents call get_company_history to retrieve information from ReplyNodes without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | query parameter |
topic | object | Yes | path parameter |
cursor | string | — | query parameter |
domain | string | Yes | Canonical registrable domain. |
Parameters from the server's own tool schema.
Why get_company_history is rated Low
Tool retrieves historical data for an entity with no modifications or side effects.
From the tool's definition Retrieve entitled Entity topic history, returns retained canonical topic history
Attacks that exploit this kind of access
The rule that runs get_company_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_company_history, this is the rule to start with:
get_company_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ReplyNodes, apply this rule, and every get_company_history call is checked against it from then on.
Questions about get_company_history
Retrieve entitled Entity topic history Returns retained canonical topic history for an entitled Entity, including history older than a Watch; unentitled access returns 404. HTTP: GET /v1/entities/{domain}/history/{topic}. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
get_company_history accepts 4 parameters: limit, topic, cursor, domain. Required: topic, domain. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for get_company_history: 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 ReplyNodes. Nothing to install.
get_company_history 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_company_history 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_company_history. 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_company_history is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue