Low Risk

get_qrcode

Get QR code for instance pairing

How to control get_qrcode ↓

What get_qrcode does on Mcp Ap2

AI agents call get_qrcode to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_qrcode needs a policy

This tool retrieves or generates a QR code for pairing instances, which is a read-only operation with no side effects. It does not create, modify, delete, execute external code, or involve financial transactions. The QR code itself is a data retrieval artifact used for authentication setup, not an action that modifies system state.

From the tool's definition Tool name 'get_qrcode' and description 'Get QR code for instance pairing' indicate a retrieval operation that generates and returns a QR code for authentication/pairing purposes. No data modification, deletion, or financial transaction occurs.

Documented attack patterns abuse exactly the kind of access get_qrcode gives an agent:

How to control get_qrcode

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_qrcode:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_qrcode": {}
  }
}

get_qrcode is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_qrcode

What does the get_qrcode tool do? +

Get QR code for instance pairing. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_qrcode? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_qrcode: 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 Mcp Ap2. Nothing to install.

What risk level is get_qrcode? +

get_qrcode is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_qrcode? +

Yes. Add a rate_limit block to the get_qrcode 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.

How do I block get_qrcode completely? +

Set action: deny in the PolicyLayer policy for get_qrcode. 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.

What MCP server provides get_qrcode? +

get_qrcode is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.