Moves the cursor to the start of the document.
AI agents use word_moveCursorToStart to create or update resources in MCP Office Interop Word Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Office Interop Word Server environment.
Although cursor positioning is reversible and has minimal destructive potential, it is a Write operation because it actively modifies the state of the document context. The severity is low because cursor movement alone cannot cause data loss or corruption—it merely repositions the editing point.
From the tool's definition Tool performs an action that modifies internal state of the document (cursor position), not a read-only retrieval.
Documented attack patterns abuse exactly the kind of access word_moveCursorToStart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Office Interop Word Server, and nothing reaches the server without passing your rules. This is the rule we recommend for word_moveCursorToStart:
{
"version": "1",
"default": "deny",
"tools": {
"word_moveCursorToStart": {
"limits": [
{
"counter": "word_movecursortostart_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}word_moveCursorToStart 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.
Moves the cursor to the start of the document. It is categorised as a Write tool in the MCP Office Interop Word Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Office Interop Word Server MCP server in PolicyLayer and add a rule for word_moveCursorToStart: 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 MCP Office Interop Word Server. Nothing to install.
word_moveCursorToStart 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 word_moveCursorToStart 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 word_moveCursorToStart. 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.
word_moveCursorToStart is provided by the MCP Office Interop Word Server MCP server (mario-andreschak/mcp-msoffice-interop-word). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Office Interop Word Server, 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.
37 MCP Office Interop Word Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.