get_sites_delta
Track changes across SharePoint sites. Returns sites that have been added, modified, or deleted since the last delta query. Pass the deltaLink from a previous response to get incremental changes.
This record as markdown: /tools/freshdesk/get-sites-delta.md
What get_sites_delta does on Freshdesk
AI agents call get_sites_delta to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_sites_delta is rated Low
Although the tool name includes 'delta' and references deletions, the verb 'Returns' and 'track changes' clarify that it only queries or retrieves historical change information. It has no side effects; it does not add, modify, or delete sites themselves. This is a read-only query operation with low blast radius if misused—an agent would only gain visibility into site changes, not cause harm.
From the tool's definition Tool retrieves change tracking data from SharePoint sites. The description states it 'Returns sites that have been added, modified, or deleted' — this is a read/query operation that 'track[s] changes' without modifying data.
Attacks that exploit this kind of access
The rule that runs get_sites_delta safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_sites_delta, this is the rule to start with:
get_sites_delta is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every get_sites_delta call is checked against it from then on.
Questions about get_sites_delta
Track changes across SharePoint sites. Returns sites that have been added, modified, or deleted since the last delta query. Pass the deltaLink from a previous response to get incremental changes. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for get_sites_delta: 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 Freshdesk. Nothing to install.
get_sites_delta is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_sites_delta 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 get_sites_delta. 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.
get_sites_delta is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue