notion_search
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/notion-search.md
What notion_search does on Integrations MCP
AI agents call notion_search 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 notion_search is rated Low
The tool name strongly suggests a search functionality, which is a read operation that queries and retrieves data from Notion without side effects. Although the description is empty, the naming convention and context of sibling tools (which include clear read operations like airtable_get_record and airtable_list_records, as well as destructive operations like airtable_delete_record) confirm this is a retrieval tool.
From the tool's definition Tool name 'notion_search' indicates a search operation against Notion. Search operations are read-only queries that retrieve data without modifying it.
Attacks that exploit this kind of access
The rule that runs notion_search 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 notion_search, this is the rule to start with:
notion_search 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 notion_search call is checked against it from then on.
Questions about notion_search
notion_search 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.
Register the Integrations MCP server in PolicyLayer and add a rule for notion_search: 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.
notion_search 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 notion_search 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 notion_search. 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.
notion_search 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