get_site_by_path

Resolve a SharePoint subsite by its relative path from a parent site. Useful for finding sites by URL structure.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_site_by_path

What does the get_site_by_path tool do? +

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.

How do I enforce a policy on get_site_by_path? +

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.

What risk level is get_site_by_path? +

get_site_by_path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_site_by_path? +

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.

How do I block get_site_by_path completely? +

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.

What MCP server provides get_site_by_path? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freshdesk's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.