List all pages for your organization in Magnet with markdown content. The organization is determined automatically from your API key. Use previewOnly=true to get markdown previews instead of full content. Supports cursor-based pagination with limit (1-100, default 50) and cursor parameters. Respo...
AI agents call list_pages to retrieve information from Magnet 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 page data from the Magnet organization. It supports pagination and optional preview mode, but performs no side effects—no creation, modification, deletion, or execution occurs. The blast radius of misuse is minimal: an agent could retrieve all pages in an organization, but cannot alter them. This is a straightforward Read operation.
From the tool's definition Tool description states it 'List all pages' and 'get markdown content' with support for 'pagination' — these are read operations with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List all pages for your organization in Magnet with markdown content. The organization is determined automatically from your API key. Use previewOnly=true to get markdown previews instead of full content. Supports cursor-based pagination with limit (1-100, default 50) and cursor parameters. Response includes pagination metadata with total count, hasMore flag, and nextCursor for fetching subsequent pages. It is categorised as a Read tool in the Magnet MCP Server, which means it retrieves data without modifying state.
Register the Magnet 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 Magnet. 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 Magnet MCP server (@magnet-ai/magnet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →