Moves the cursor by the specified unit and count.
AI agents invoke word_moveCursor to trigger actions in MCP Office Interop Word Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Moving the cursor in a Word document via COM Interop is an active operation that changes the state of the application (selection/cursor position), triggering external operations in the Word process. It doesn't read data or write/modify document content directly, but it executes a programmatic action within the Word COM interface that affects subsequent operations.
From the tool's definition Moves the cursor by the specified unit and count
Documented attack patterns abuse exactly the kind of access word_moveCursor 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_moveCursor:
{
"version": "1",
"default": "deny",
"tools": {
"word_moveCursor": {
"limits": [
{
"counter": "word_movecursor_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} word_moveCursor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Moves the cursor by the specified unit and count. It is categorised as a Execute tool in the MCP Office Interop Word Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Office Interop Word Server MCP server in PolicyLayer and add a rule for word_moveCursor: 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_moveCursor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the word_moveCursor 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_moveCursor. 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_moveCursor 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.