voog_ecommerce_api_call · Voog MCP: Risk & Policy

WHAT IT DOES

What voog_ecommerce_api_call does on Voog

AI agents invoke voog_ecommerce_api_call to trigger actions in Voog. 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 voog_ecommerce_api_call needs a policy

This is a generic API passthrough that forwards arbitrary HTTP requests to the Ecommerce API. It can trigger any operation (read, write, delete, financial) depending on the method and endpoint passed as arguments. Since it spans multiple categories, the most severe applicable is chosen.

From the tool's definition Generic Ecommerce v1 API passthrough. Forward an HTTP

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

voog_ecommerce_api_call Rate-limited

voog_ecommerce_api_call 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": {
    "voog_ecommerce_api_call": {
      "limits": [
        {
          "counter": "voog_ecommerce_api_call_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 Voog, so you can run agents against it safely.

FAQ

Questions about voog_ecommerce_api_call

What does the voog_ecommerce_api_call tool do? +

Generic Ecommerce v1 API passthrough. Forward an HTTP. It is categorised as a Execute tool in the Voog MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on voog_ecommerce_api_call? +

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

What risk level is voog_ecommerce_api_call? +

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

Can I rate-limit voog_ecommerce_api_call? +

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

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

voog_ecommerce_api_call is provided by the Voog MCP server (runnel/voog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.