Create a new Freshservice asset
AI agents use create_asset 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 an asset is a write operation that adds data to the system reversibly. While it modifies organizational data managed by Freshservice, it does not delete, overwrite, or execute arbitrary code. The risk is medium because misuse could lead to asset inventory pollution or unauthorized asset registration, but the operation is non-destructive and potentially remediable through deletion.
From the tool's definition Tool is named 'create_asset' with description 'Create a new Freshservice asset'. This creates new records in the Freshservice ITSM system without deleting or overwriting existing data.
Attacks that exploit this kind of access
Create a new Freshservice asset. 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_asset: 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_asset 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_asset 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_asset. 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_asset is provided by the Freshservice MCP Server MCP server (tannertm0/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 →