deploy_web_server · OCI MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_web_server does on OCI MCP Server

AI agents invoke deploy_web_server to trigger actions in OCI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why deploy_web_server needs a policy

This tool executes a multi-step orchestration that triggers external operations (instance launch, networking config, web server setup) whose effects depend on arguments and cannot be trivially reversed. While not strictly destructive (infrastructure can be torn down), it goes far beyond Read or Write; it runs provisioning logic with significant blast radius.

From the tool's definition Tool deploys a full web server stack (VCN, IGW, route, seclist, subnet, nginx instance) with public IP exposure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_web_server Rate-limited

deploy_web_server stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_web_server": {
      "limits": [
        {
          "counter": "deploy_web_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about deploy_web_server

What does the deploy_web_server tool do? +

One-shot: VCN+IGW+route+seclist+subnet+nginx instance. Returns public_ip + URL. It is categorised as a Execute tool in the OCI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_web_server? +

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

What risk level is deploy_web_server? +

deploy_web_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_web_server? +

Yes. Add a rate_limit block to the deploy_web_server 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 deploy_web_server completely? +

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

deploy_web_server is provided by the OCI MCP Server MCP server (sarthak-pansare/oci-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.