create_qr_code_with_options
AI agents use create_qr_code_with_options to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Creating a QR code is a reversible write operation that generates new data (an image/artifact) without side effects on existing systems. It does not execute external code, delete data, or involve financial transactions. The 'create' verb places this in the Write category. Severity is low because QR code generation is a benign utility function with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'create_qr_code_with_options' indicates creation of a QR code artifact. Description is empty, but the verb 'create' and tool purpose suggest data generation.
Attacks that exploit this kind of access
create_qr_code_with_options. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for create_qr_code_with_options: 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 Integrations MCP. Nothing to install.
create_qr_code_with_options 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 create_qr_code_with_options 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 create_qr_code_with_options. 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.
create_qr_code_with_options is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →