Low Risk

get_site_by_path

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

How to control get_site_by_path ↓

What get_site_by_path does on Apple Shortcuts

AI agents call get_site_by_path to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_site_by_path needs a policy

This tool retrieves or queries SharePoint site metadata by path without modifying data, executing code, or triggering side effects. It is a read-only lookup operation analogous to a directory search. The low severity reflects minimal blast radius even if misused by an AI agent—at worst it reveals organizational structure that may already be accessible.

From the tool's definition Tool name 'get_site_by_path' and description 'Resolve a SharePoint subsite by its relative path from a parent site' indicate a lookup/query operation.

Documented attack patterns abuse exactly the kind of access get_site_by_path gives an agent:

How to control get_site_by_path

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for get_site_by_path:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_site_by_path": {}
  }
}

get_site_by_path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Apple Shortcuts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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 Apple Shortcuts MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_site_by_path? +

Register the Apple Shortcuts 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 Apple Shortcuts. 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 Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Shortcuts tool call.

Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.