get_recent_company_events

List entitled Company Changes events Lists canonical Events covered by the organization's current or retained Watch topic subscriptions. HTTP: GET /v1/events

SERVERReplyNodes SOURCEhttps://mcp.replynodes.com/mcp

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-replynodes-mcp/get-recent-company-events.md

WHAT IT DOES

What get_recent_company_events does on ReplyNodes

AI agents call get_recent_company_events 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
`type`	string	—	query parameter
`limit`	integer	—	query parameter
`since`	string	—	RFC3339 or a relative 24h/30d window
`topic`	string	—	query parameter
`until`	string	—	RFC3339 or a relative 24h/30d window
`cursor`	string	—	query parameter
`entity`	string	—	query parameter
`watch_id`	string	—	query parameter

Parameters from the server's own tool schema.

RISK

Why get_recent_company_events is rated Low

Queries company event data via read-only GET endpoint; no side effects or modifications.

From the tool's definition List entitled Company Changes events; GET /v1/events; retrieves data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_recent_company_events 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_recent_company_events, this is the rule to start with:

get_recent_company_events Allowed

get_recent_company_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recent_company_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ReplyNodes, apply this rule, and every get_recent_company_events call is checked against it from then on.

FAQ

Questions about get_recent_company_events

What does the get_recent_company_events tool do? +

List entitled Company Changes events Lists canonical Events covered by the organization's current or retained Watch topic subscriptions. HTTP: GET /v1/events. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.

What parameters does get_recent_company_events accept? +

get_recent_company_events accepts 8 parameters: type, limit, since, topic, until, cursor, entity, watch_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_recent_company_events? +

Register the ReplyNodes MCP server in PolicyLayer and add a rule for get_recent_company_events: 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.

What risk level is get_recent_company_events? +

get_recent_company_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_company_events? +

Yes. Add a rate_limit block to the get_recent_company_events 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.

How do I block get_recent_company_events completely? +

Set action: deny in the PolicyLayer policy for get_recent_company_events. 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.

What MCP server provides get_recent_company_events? +

get_recent_company_events 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.

KEEP EXPLORING

More on ReplyNodes, and thousands of servers like it.

This server

All 66 ReplyNodes tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →