Get a SharePoint site by hostname and path
AI agents call get_site_by_url to retrieve information from Microsoft Graph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about a SharePoint site without creating, modifying, deleting, or executing operations. It is a straightforward read operation that returns site metadata based on input parameters. The blast radius if misused is minimal—an unauthorized query would only expose site information the caller shouldn't access, not trigger destructive or financial consequences.
From the tool's definition Tool name 'get_site_by_url' and description 'Get a SharePoint site by hostname and path' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a SharePoint site by hostname and path. It is categorised as a Read tool in the Microsoft Graph MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for get_site_by_url: 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 Microsoft Graph MCP Server. Nothing to install.
get_site_by_url 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_url 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_url. 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_url is provided by the Microsoft Graph MCP Server MCP server (ry-ops/microsoft-graph-mcp-server). 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 →