List Cosense pages in the project.
AI agents call list_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 retrieves and queries a list of pages from a Cosense project without creating, modifying, or deleting any data. It is a standard read operation with minimal security risk - the worst case is information disclosure about what pages exist in a project, which is typically low-severity.
From the tool's definition Tool name 'list_pages' combined with description 'List Cosense pages in the project' indicates a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access list_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 list_pages:
{
"version": "1",
"default": "deny",
"tools": {
"list_pages": {}
}
}list_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.
List Cosense pages in the 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 list_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.
list_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 list_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 list_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.
list_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.