AI agents use infoset_create_ticket to create or update resources in Infoset — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infoset environment.
This tool creates a new ticket record in the Infoset CRM, modifying system state reversibly. It is a Write operation (not Read, as it changes data; not Execute, as it doesn't run arbitrary code; not Destructive, as ticket creation is reversible via deletion; not Financial, as it doesn't involve payments).
From the tool's definition Tool name is 'infoset_create_ticket' and description states 'Create a new Infoset ticket', which creates a new data record in the CRM system.
Attacks that exploit this kind of access
Create a new Infoset ticket. It is categorised as a Write tool in the Infoset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Infoset MCP server in PolicyLayer and add a rule for infoset_create_ticket: 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 Infoset. Nothing to install.
infoset_create_ticket 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 infoset_create_ticket 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 infoset_create_ticket. 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.
infoset_create_ticket is provided by the Infoset MCP server (sudohakan/infoset-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 →