get_site_by_path
Resolve a SharePoint subsite by its relative path from a parent site. Useful for finding sites by URL structure.
This record as markdown: /tools/freshdesk/get-site-by-path.md
What get_site_by_path does on Freshdesk
AI agents call get_site_by_path 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_site_by_path is rated Low
This tool retrieves information about SharePoint subsites based on path parameters. It performs a read-only lookup operation to discover or navigate site structures. No data is created, modified, deleted, or code executed. The blast radius of misuse is minimal—an agent could only enumerate or access SharePoint site metadata it may already have permission to view.
From the tool's definition Tool description states it 'Resolve[s] a SharePoint subsite' and is 'Useful for finding sites by URL structure.' The verb 'Resolve' and context of 'finding' indicate a query/lookup operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_site_by_path 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_site_by_path, this is the rule to start with:
get_site_by_path 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_site_by_path call is checked against it from then on.
Questions about get_site_by_path
Resolve a SharePoint subsite by its relative path from a parent site. Useful for finding sites by URL structure. 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_site_by_path: 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_site_by_path 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_site_by_path 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_site_by_path. 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_site_by_path 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