Search for pages containing the specified query string in the Cosense project.
AI agents call search_pages to retrieve information from Cosense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation across existing pages to find matches, which is a fundamental read operation. It has no side effects, does not modify data, execute code, or delete anything. The query parameter may influence results but does not alter state. Blast radius is minimal—misuse would only expose existing information the user already has access to in their Cosense project.
From the tool's definition Tool description states 'Search for pages containing the specified query string in the Cosense project.' The verb 'search' and the operation of querying pages for content matches are read-only operations that retrieve information without modification.
Documented attack patterns abuse exactly the kind of access search_pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cosense, and nothing reaches the server without passing your rules. This is the rule we recommend for search_pages:
{
"version": "1",
"default": "deny",
"tools": {
"search_pages": {}
}
}search_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for pages containing the specified query string in the Cosense project. It is categorised as a Read tool in the Cosense MCP Server, which means it retrieves data without modifying state.
Register the Cosense MCP server in PolicyLayer and add a rule for search_pages: 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 Cosense. Nothing to install.
search_pages 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_pages 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_pages. 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_pages is provided by the Cosense MCP server (yosider/cosense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cosense, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Cosense tools catalogued and risk-classified — across an index of 43,000+ MCP servers.