加密文档 Args: doc_path: 要加密的文档路径 password: 加密密码 Returns: 包含加密结果的字典
AI agents use encrypt_document to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.
Encryption is a modification operation that alters document state reversibly. While it affects document accessibility, it does not delete data (Destructive), execute arbitrary code (Execute), create financial transactions (Financial), or merely read data (Read). It fits Write category as a document property modification.
From the tool's definition Tool name is 'encrypt_document' with args 'doc_path' and 'password'. Description translates to 'Encrypt document' with return of encryption result dictionary.
Documented attack patterns abuse exactly the kind of access encrypt_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for encrypt_document:
{
"version": "1",
"default": "deny",
"tools": {
"encrypt_document": {
"limits": [
{
"counter": "encrypt_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}encrypt_document 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.
加密文档 Args: doc_path: 要加密的文档路径 password: 加密密码 Returns: 包含加密结果的字典. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office Editor MCP server in PolicyLayer and add a rule for encrypt_document: 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 Office Editor. Nothing to install.
encrypt_document 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 encrypt_document 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 encrypt_document. 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.
encrypt_document is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.