Export the most recent timeline analysis to files (JSON and Markdown).
AI agents use export_results to create or update resources in Zoho Timeline MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zoho Timeline MCP Server environment.
This tool creates new files (JSON and Markdown exports) representing write operations. While not destructive since exports can be overwritten without irreversible loss, and not as severe as code execution, it modifies the filesystem by writing data.
From the tool's definition Tool performs export operations that create and write files in JSON and Markdown formats. The description states 'Export the most recent timeline analysis to files' which indicates file creation/modification.
Attacks that exploit this kind of access
Export the most recent timeline analysis to files (JSON and Markdown). It is categorised as a Write tool in the Zoho Timeline MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zoho Timeline MCP Server MCP server in PolicyLayer and add a rule for export_results: 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 Zoho Timeline MCP Server. Nothing to install.
export_results 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_results 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_results. 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_results is provided by the Zoho Timeline MCP Server MCP server (johnelamont/zoho-timeline-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 →