AI agents use apply_preset to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
preset_id | string | Yes | Preset ID to apply |
Parameters from the server's own tool schema.
This tool modifies project configuration reversibly by applying a preset that overwrites statuses and transitions. While it changes existing data, it is not irreversible (a different preset could be applied, or the original could be restored), and it does not delete data — it reconfigures it. This qualifies as Write rather than Destructive.
From the tool's definition Tool description states it 'Apply[s] a workflow preset to a project (replaces current statuses and transitions)' — this modifies project configuration by replacing existing workflow state. The verb 'replaces' indicates overwrite of existing data structures.
Attacks that exploit this kind of access
Apply a workflow preset to a project (replaces current statuses and transitions). It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
apply_preset accepts 2 parameters: project, preset_id. Required: project, preset_id. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for apply_preset: 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 Tickr. Nothing to install.
apply_preset 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 apply_preset 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 apply_preset. 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.
apply_preset is provided by the Tickr MCP server (@k-system/tickr-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 →