Retrieve full details of a published micro-landing page by its ID. Returns the page title, public URL (via its associated short link), HTML content, publish status, version history, and the short link code used for QR code generation. Use this to verify a landing page was published correctly, ret...
Single-target operation
Part of the Qr Maker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_landing to retrieve information from Qr Maker 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_landing 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_landing:
rules:
- action: allowSee the full Qr Maker policy for all 19 tools.
Agents calling read-class tools like get_landing 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 full details of a published micro-landing page by its ID. Returns the page title, public URL (via its associated short link), HTML content, publish status, version history, and the short link code used for QR code generation. Use this to verify a landing page was published correctly, retrieve its public URL to share or encode in a QR, or inspect its current content before calling update_landing. The landing_id is returned by publish_landing when the page is created.. It is categorised as a Read tool in the Qr Maker MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_landing. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Qr Maker MCP server.
get_landing 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_landing 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_landing. 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_landing is provided by the Qr Maker MCP server (@qr-maker/mcp-server). 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