Retrieve the full content of a specific knowledge base page by its exact ID. Other tools return [PageID] citations in their responses. If you need more detail from a cited page, call this tool with that page ID to get the full content. Use this tool when you: - See a [PageID] citation in a resp...
Single-target operation
Part of the Leeroopedia MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_page to retrieve information from Leeroopedia without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_page only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_page:
rules:
- action: allowSee the full Leeroopedia policy for all 8 tools.
Agents calling read-class tools like get_page have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieve the full content of a specific knowledge base page by its exact ID. Other tools return [PageID] citations in their responses. If you need more detail from a cited page, call this tool with that page ID to get the full content. Use this tool when you: - See a [PageID] citation in a response and want the full page content - Need deeper detail than what was included in a synthesized answer - Want to read a specific page directly without searching Returns the page formatted as markdown, or an error if the page ID is not found.. It is categorised as a Read tool in the Leeroopedia MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_page. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Leeroopedia MCP server.
get_page 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 get_page rule in your Intercept 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 Intercept policy for get_page. 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.
get_page is provided by the Leeroopedia MCP server (leeroopedia/leeroopedia). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept