Gpg_Encrypt_File
Encrypt a file with GPG and save it to a destination path.
This record as markdown: /tools/com-files-python-mcp/gpg-encrypt-file.md
What Gpg_Encrypt_File does on Files Com
AI agents use Gpg_Encrypt_File to create or update resources in Files Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Files Com environment.
Why Gpg_Encrypt_File is rated Medium
This tool writes encrypted data to the filesystem by design. While encryption itself is a computational operation, the primary effect is persisting new encrypted file data to storage. This is reversible (the file can be deleted or overwritten later), so it falls under Write rather than Destructive.
From the tool's definition Tool description states 'Encrypt a file with GPG and save it to a destination path.' The action of saving/writing encrypted content to a destination path constitutes data creation/modification.
Attacks that exploit this kind of access
The rule that runs Gpg_Encrypt_File safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Gpg_Encrypt_File, this is the rule to start with:
Gpg_Encrypt_File 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 Files Com, apply this rule, and every Gpg_Encrypt_File call is checked against it from then on.
Questions about Gpg_Encrypt_File
Encrypt a file with GPG and save it to a destination path. It is categorised as a Write tool in the Files Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Files Com MCP server in PolicyLayer and add a rule for Gpg_Encrypt_File: 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 Files Com. Nothing to install.
Gpg_Encrypt_File 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 Gpg_Encrypt_File 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 Gpg_Encrypt_File. 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.
Gpg_Encrypt_File is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue