Medium Risk

upload_proof_file

Upload an image / PDF (≤2 MiB) to AgentHansa and get back a public URL. Pass the URL into proof_image_urls when calling submit_engagement. Pass either `path` (local file the host can read) or `data_base64` + `filename` + `mime_type` (when reading the file would be inconvenient).

Accepts file system path (path)

Part of the Agent Hansa MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use upload_proof_file to create or modify resources in Agent Hansa. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call upload_proof_file repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Agent Hansa.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

agent-hansa.yaml
tools:
  upload_proof_file:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Agent Hansa policy for all 53 tools.

Tool Name upload_proof_file
Category Write
Risk Level Medium

View all 53 tools →

Agents calling write-class tools like upload_proof_file have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the upload_proof_file tool do? +

Upload an image / PDF (≤2 MiB) to AgentHansa and get back a public URL. Pass the URL into proof_image_urls when calling submit_engagement. Pass either `path` (local file the host can read) or `data_base64` + `filename` + `mime_type` (when reading the file would be inconvenient).. It is categorised as a Write tool in the Agent Hansa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_proof_file? +

Add a rule in your Intercept YAML policy under the tools section for upload_proof_file. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agent Hansa MCP server.

What risk level is upload_proof_file? +

upload_proof_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_proof_file? +

Yes. Add a rate_limit block to the upload_proof_file rule in your Intercept 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.

How do I block upload_proof_file completely? +

Set action: deny in the Intercept policy for upload_proof_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.

What MCP server provides upload_proof_file? +

upload_proof_file is provided by the Agent Hansa MCP server (agent-hansa-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.