AI agents use sort_range to create or update resources in Libreoffice — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Libreoffice environment.
Sorting a range in a spreadsheet or table reorders data in place, which is a Write operation (reversible modification). While not destructive, it can affect dependent formulas, conditional formatting, and data integrity if users rely on original ordering. Medium severity reflects potential confusion or workflow disruption but reversibility and typical use cases. Lower confidence due to absent description.
From the tool's definition Tool named 'sort_range' on a LibreOffice document server; sorting modifies data order within a range, which constitutes reversible data modification. Description is empty, reducing confidence slightly.
Documented attack patterns abuse exactly the kind of access sort_range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Libreoffice, and nothing reaches the server without passing your rules. This is the rule we recommend for sort_range:
{
"version": "1",
"default": "deny",
"tools": {
"sort_range": {
"limits": [
{
"counter": "sort_range_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sort_range 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.
Free to start. No card required.
sort_range. It is categorised as a Write tool in the Libreoffice MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Libreoffice MCP server in PolicyLayer and add a rule for sort_range: 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 Libreoffice. Nothing to install.
sort_range 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 sort_range 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 sort_range. 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.
sort_range is provided by the Libreoffice MCP server (waterpistolai/libreoffice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Libreoffice, 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.
24 Libreoffice tools catalogued and risk-classified — across an index of 43,000+ MCP servers.