AI agents use export_responses to create or update resources in Tickiti — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickiti environment.
This tool creates a new file on the local system containing response data exported from the helpdesk system. While not destructive (the original data remains), it is a write operation that creates persistent file artifacts.
From the tool's definition Tool description states 'Dump every response matching the filters to a local NDJSON file', indicating it writes data to a local file system. The action of exporting/dumping data to a file is a write operation that creates new data artifacts.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Dump every response matching the filters to a local NDJSON file (one JSON. It is categorised as a Write tool in the Tickiti MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tickiti MCP server in PolicyLayer and add a rule for export_responses: 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 Tickiti. Nothing to install.
export_responses 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 export_responses 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 export_responses. 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.
export_responses is provided by the Tickiti MCP server (tickiti/tickiti-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 →