Generate a QR code (PNG base64 or SVG)
AI agents use qr_generate to create or update resources in Agent Toolbox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Toolbox environment.
An AI agent can call qr_generate faster than any human can review — one bad instruction and it creates or modifies resources in Agent Toolbox by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Generate a QR code (PNG base64 or SVG). It is categorised as a Write tool in the Agent Toolbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Toolbox MCP server in PolicyLayer and add a rule for qr_generate: 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 Agent Toolbox. Nothing to install.
qr_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the qr_generate 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 qr_generate. 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.
qr_generate is provided by the Agent Toolbox MCP server (vincentwei1021/agent-toolbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.