Get a file from objekt.sh by name. Returns a link to the file without downloading the content.
AI agents call get_file to retrieve information from Mcp Upload without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file metadata/links without modifying, deleting, or executing anything. It is a simple read/query operation with minimal blast radius. The fact that it returns a link rather than downloading content further confirms it is a non-destructive retrieval action.
From the tool's definition Tool description states 'Get a file from objekt.sh by name. Returns a link to the file without downloading the content.' — retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a file from objekt.sh by name. Returns a link to the file without downloading the content. It is categorised as a Read tool in the Mcp Upload MCP Server, which means it retrieves data without modifying state.
Register the Mcp Upload MCP server in PolicyLayer and add a rule for get_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 Mcp Upload. Nothing to install.
get_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_file is provided by the Mcp Upload MCP server (@objekt.sh/mcp-upload). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_file is one line of Mcp Upload's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →