Update the state of an Intercom ticket.
AI agents use update_ticket_state to create or update resources in Intercom Articles MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intercom Articles MCP Server environment.
Updating a ticket's state is a reversible write operation—it modifies an existing record without permanently deleting it or executing arbitrary code. While state changes could affect business workflows (e.g., closing a support ticket), the operation remains reversible and does not move money or irreversibly destroy data.
From the tool's definition Tool name 'update_ticket_state' and description 'Update the state of an Intercom ticket' indicate modification of existing data (ticket state changes). The server description emphasizes 'full CRUD operations' with 'update' as a core capability.
Documented attack patterns abuse exactly the kind of access update_ticket_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intercom Articles MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_ticket_state:
{
"version": "1",
"default": "deny",
"tools": {
"update_ticket_state": {
"limits": [
{
"counter": "update_ticket_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_ticket_state stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the state of an Intercom ticket. It is categorised as a Write tool in the Intercom Articles MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intercom Articles MCP Server MCP server in PolicyLayer and add a rule for update_ticket_state: 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 Intercom Articles MCP Server. Nothing to install.
update_ticket_state 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 update_ticket_state 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 update_ticket_state. 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.
update_ticket_state is provided by the Intercom Articles MCP Server MCP server (kaosensei/intercom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intercom Articles MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Intercom Articles MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.