create_character
AI agents use create_character 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 a new character entity in the game, which is a reversible write operation. No destructive action, code execution, or financial impact. The game context and absence of any irreversible language keeps severity low. Confidence is moderate due to missing description, but the name and context are clear enough to classify confidently as Write.
From the tool's definition Tool name 'create_character' indicates data creation. Description is empty, limiting specificity, but context from sibling tools (attack, defend, equip, examine, explore, flee, load_game, move, pickup) confirms this is a game state management tool in a…
Attacks that exploit this kind of access
create_character. 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 create_character: 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.
create_character 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_character 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_character. 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_character 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 →