Low Risk

get_info

Get metadata of file in OpenDAL service

How to control get_info ↓

AI agents call get_info to retrieve information from MCP Server for Apache OpenDAL™ without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves metadata information about files from storage services, which is a read-only operation with no side effects. It does not modify, delete, or execute any operations—it simply queries and returns information about existing files. The low severity reflects minimal risk even if misused, as metadata retrieval alone cannot alter data or trigger external actions.

From the tool's definition Tool name 'get_info' and description 'Get metadata of file in OpenDAL service' indicate retrieval of file metadata without modification or deletion.

Documented attack patterns abuse exactly the kind of access get_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Apache OpenDAL™, and nothing reaches the server without passing your rules. This is the rule we recommend for get_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_info": {}
  }
}

get_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Server for Apache OpenDAL™ — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_info tool do? +

Get metadata of file in OpenDAL service. It is categorised as a Read tool in the MCP Server for Apache OpenDAL™ MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_info? +

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

What risk level is get_info? +

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

Can I rate-limit get_info? +

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

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

get_info is provided by the MCP Server for Apache OpenDAL™ MCP server (xuanwo/mcp-server-opendal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for Apache OpenDAL™ tool call.

Deterministic rules across all 3 MCP Server for Apache OpenDAL™ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

3 MCP Server for Apache OpenDAL™ tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.