Create a note for a ticket in Freshservice.
AI agents use create_ticket_note to create or update resources in Freshservice MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshservice MCP Server environment.
Creating a ticket note is a reversible modification that adds information to a ticket without deleting or overwriting existing data. It has medium severity because while it creates data, the impact is limited to adding a note—it doesn't execute external code, move money, or delete information.
From the tool's definition Tool creates a note for a ticket, which is a write operation that adds new data to an existing ticket record in Freshservice.
Attacks that exploit this kind of access
Create a note for a ticket in Freshservice. It is categorised as a Write tool in the Freshservice MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for create_ticket_note: 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 Freshservice MCP Server. Nothing to install.
create_ticket_note 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_ticket_note 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_ticket_note. 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_ticket_note is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_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 →