This record as markdown: /tools/io-github-portel-dev-ncp/search-content.md
What search_content does on Ncp
AI agents call search_content to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_content is rated Low
This tool performs a search operation on Confluence, which is a read-only action that retrieves information without side effects. Searching does not create, modify, delete, or execute any operations—it simply queries and returns existing content. This is a classic Read category tool with low severity since misuse would only expose existing data already accessible to the user in Confluence.
From the tool's definition Tool name 'search_content' and description 'Search Confluence content' indicate a query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
The rule that runs search_content safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_content, this is the rule to start with:
search_content 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 Ncp, apply this rule, and every search_content call is checked against it from then on.
Questions about search_content
Search Confluence content. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for search_content: 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 Ncp. Nothing to install.
search_content 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 search_content 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 search_content. 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.
search_content is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue