Pick up an item or connector from the current room.
AI agents use pickup to create or update resources in Integration Quest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integration Quest environment.
The tool creates or modifies game state (inventory) reversibly. It does not execute arbitrary code, delete data permanently, move money, or merely read information. It fits the Write category as a create/modify action. Severity is low because the blast radius is confined to a single-player RPG simulation with no external side effects or real-world consequences.
From the tool's definition Tool performs a state-changing action: 'pick up an item or connector from the current room' modifies the character's inventory/game state by adding an item. This is a reversible modification (items can be dropped).
Attacks that exploit this kind of access
Pick up an item or connector from the current room. It is categorised as a Write tool in the Integration Quest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integration Quest MCP server in PolicyLayer and add a rule for pickup: 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 Integration Quest. Nothing to install.
pickup 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 pickup 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 pickup. 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.
pickup is provided by the Integration Quest MCP server (mattcarpenter-workato/workato-integration-quest). 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 →