High Risk →

tool_sa_airport_oracle

POST /tools/sa-airport-oracle/run — Returns live flight status from ACSA (airports.co.za). Input: {airport_code: 'JNB'|'CPT'|'DUR', flight_number: string, request_type: 'arrival'|'departure'}. Output: {success, live_status, scheduled_time, estimated_time, actual_time, gate, carousel, terminal, fl...

Part of the Agent Vending Factory server.

tool_sa_airport_oracle can trigger actions in Agent Vending Factory, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AGENT VENDING FACTORY →

Free to start. No card required.

AI agents invoke tool_sa_airport_oracle to trigger processes or run actions in Agent Vending Factory. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

tool_sa_airport_oracle can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tool_sa_airport_oracle": {
      "limits": [
        {
          "counter": "tool_sa_airport_oracle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Agent Vending Factory policy for all 6 tools.

Get this rule live on your own Agent Vending Factory server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGENT VENDING FACTORY →

These attack patterns abuse exactly the kind of access tool_sa_airport_oracle gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so tool_sa_airport_oracle only ever does what you allow.

SECURE AGENT VENDING FACTORY →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the tool_sa_airport_oracle tool do? +

POST /tools/sa-airport-oracle/run — Returns live flight status from ACSA (airports.co.za). Input: {airport_code: 'JNB'|'CPT'|'DUR', flight_number: string, request_type: 'arrival'|'departure'}. Output: {success, live_status, scheduled_time, estimated_time, actual_time, gate, carousel, terminal, flight_number, airport_code, request_type, error}. Coverage: JNB (O.R. Tambo), CPT (Cape Town Int'l), DUR (King Shaka). Data window: flights within 48 hours. Call GET /tools/sa-airport-oracle/health (free) first — if structure_valid=false, do not proceed. error_type values: 'stale_data' (do not retry), 'not found' (retry after 10-15 min), network error (retry once). flight_number is case-insensitive and normalised to uppercase internally. Read-only — no booking/ticketing. Cost: $0.1200 USDC per call.. It is categorised as a Execute tool in the Agent Vending Factory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tool_sa_airport_oracle? +

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

What risk level is tool_sa_airport_oracle? +

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

Can I rate-limit tool_sa_airport_oracle? +

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

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

tool_sa_airport_oracle is provided by the Agent Vending Factory MCP server (https://agent-vending-factory-3srpjtr7na-ew.a.run.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Vending Factory tool call.

Deterministic rules across all 6 Agent Vending Factory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.