bounding_box

A read tool on the CLIO Adios MCP server.

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/bounding-box.md

WHAT IT DOES

What bounding_box does on CLIO Adios

AI agents call bounding_box to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why bounding_box is rated Low

Bounding box operations typically retrieve or filter data within spatial bounds without modifying underlying data. The empty description reduces confidence, but the server's stated purpose (fetch and analyze) and sibling tool patterns (all appear to be analysis/read operations) suggest this is a read operation. No evidence of data modification, deletion, execution, or financial operations.

From the tool's definition Tool name 'bounding_box' with empty description suggests spatial data querying or filtering. Context includes 'Fetch and analyze BP5 data files' and sibling tools like 'analyze_file_access_patterns' and 'analyze_posix_operations', indicating read-only data…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bounding_box safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bounding_box, this is the rule to start with:

bounding_box Allowed

bounding_box is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bounding_box": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every bounding_box call is checked against it from then on.

FAQ

Questions about bounding_box

What does the bounding_box tool do? +

bounding_box is a read tool on the CLIO Adios MCP server. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bounding_box? +

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

What risk level is bounding_box? +

bounding_box is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bounding_box? +

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

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

bounding_box is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →