search_sharepoint
Search across all SharePoint sites, document libraries, lists, and list items. More powerful than search_library_files which only searches within a single library.
This record as markdown: /tools/freshdesk/search-sharepoint.md
What search_sharepoint does on Freshdesk
AI agents call search_sharepoint 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 search_sharepoint is rated Low
The tool performs a search operation across SharePoint resources. The verb 'search' and the phrase 'search across' clearly indicate data retrieval without side effects. There is no mention of creating, modifying, deleting, or executing code. The severity is low because while a compromised agent could retrieve sensitive documents, the tool itself cannot modify or delete data, limiting the blast radius.
From the tool's definition Tool name 'search_sharepoint' and description 'Search across all SharePoint sites, document libraries, lists, and list items' indicate a query/retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs search_sharepoint 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 search_sharepoint, this is the rule to start with:
search_sharepoint 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 search_sharepoint call is checked against it from then on.
Questions about search_sharepoint
Search across all SharePoint sites, document libraries, lists, and list items. More powerful than search_library_files which only searches within a single library. 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 search_sharepoint: 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.
search_sharepoint 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 search_sharepoint 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 search_sharepoint. 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.
search_sharepoint 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