upload_company_document · OOSDK MCP Server MCP

WHAT IT DOES

What upload_company_document does on OOSDK MCP Server

AI agents use upload_company_document to create or update resources in OOSDK MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OOSDK MCP Server environment.

WHY IT NEEDS A POLICY

Why upload_company_document needs a policy

The 'upload' verb indicates a write operation that creates or adds data to the system. Uploading a document modifies the document repository by introducing new content. This is reversible (can be deleted), so it does not rise to Destructive.

From the tool's definition Tool name 'upload_company_document' indicates file creation/storage. Related tools on the server include 'delete_company_document' (destructive), suggesting document lifecycle management. Description is empty, reducing certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_company_document Rate-limited

upload_company_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_company_document": {
      "limits": [
        {
          "counter": "upload_company_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OOSDK MCP Server, so you can run agents against it safely.

FAQ

Questions about upload_company_document

What does the upload_company_document tool do? +

upload_company_document. It is categorised as a Write tool in the OOSDK MCP Server 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_company_document? +

Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for upload_company_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 OOSDK MCP Server. Nothing to install.

What risk level is upload_company_document? +

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

Can I rate-limit upload_company_document? +

Yes. Add a rate_limit block to the upload_company_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.

How do I block upload_company_document completely? +

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

What MCP server provides upload_company_document? +

upload_company_document is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.