get_top_stories
Fetch the current top stories from Hacker News.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/get-top-stories.md
What get_top_stories does on Integrations MCP
AI agents call get_top_stories to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_top_stories is rated Low
This tool retrieves publicly available news stories from Hacker News without creating, modifying, deleting, or executing any operations. It is a simple data query operation with no blast radius if misused by an AI agent, as it only reads public information.
From the tool's definition Tool name 'get_top_stories' and description 'Fetch the current top stories from Hacker News' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_top_stories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_top_stories, this is the rule to start with:
get_top_stories 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 Integrations MCP, apply this rule, and every get_top_stories call is checked against it from then on.
Questions about get_top_stories
Fetch the current top stories from Hacker News. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for get_top_stories: 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 Integrations MCP. Nothing to install.
get_top_stories 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_top_stories 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_top_stories. 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_top_stories is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue