rename_library_item
Rename a file or folder in a SharePoint document library.
This record as markdown: /tools/freshdesk/rename-library-item.md
What rename_library_item does on Freshdesk
AI agents use rename_library_item to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why rename_library_item is rated Medium
Renaming files or folders modifies data structures but does not delete, destroy, or create new content; the operation is reversible (can be renamed back). This is a Write operation. Severity is medium because renaming could cause confusion or break dependent references if done maliciously, but the impact is limited to organizational structure rather than data loss or financial harm.
From the tool's definition Tool description states 'Rename a file or folder in a SharePoint document library' — the action of renaming is a reversible modification of metadata/naming attributes.
Attacks that exploit this kind of access
The rule that runs rename_library_item 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 rename_library_item, this is the rule to start with:
rename_library_item stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 rename_library_item call is checked against it from then on.
Questions about rename_library_item
Rename a file or folder in a SharePoint document library. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for rename_library_item: 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.
rename_library_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_library_item 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 rename_library_item. 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.
rename_library_item 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