search_stories

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/search-stories.md

WHAT IT DOES

What search_stories does on Integrations MCP

AI agents call search_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.

RISK

Why search_stories is rated Low

The name strongly suggests this tool retrieves or searches for stories from a data store without modifying or deleting data. Search and query operations are typical Read category tools. However, confidence is moderate (0.6) due to the empty description—without more details about what 'stories' refers to or its actual behavior, we cannot rule out that it might have side effects or be part of a destructive workflow.

From the tool's definition Tool name 'search_stories' indicates a query/search operation. The description is empty, limiting direct evidence of its functionality.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_stories Allowed

search_stories 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": {
    "search_stories": {}
  }
}

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

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

FAQ

Questions about search_stories

What does the search_stories tool do? +

search_stories is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_stories? +

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

What risk level is search_stories? +

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

Can I rate-limit search_stories? +

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

How do I block search_stories completely? +

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

What MCP server provides search_stories? +

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

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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