data_tables

List tables/collections across any supported backend.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/data-tables.md

WHAT IT DOES

What data_tables does on Yaver

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

Parameter	Type	Required	Description
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why data_tables is rated Low

This tool queries and enumerates database schema artifacts (tables/collections) but does not modify, delete, execute code, or perform financial operations. It is a simple informational read that would have minimal blast radius if misused by an AI agent — at worst, it reveals what data structures exist in the backend.

From the tool's definition Tool name 'data_tables' and description 'List tables/collections across any supported backend' indicate a retrieval operation with no modification, deletion, or execution capability.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs data_tables safely

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

data_tables Allowed

data_tables 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": {
    "data_tables": {}
  }
}

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

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

FAQ

Questions about data_tables

What does the data_tables tool do? +

List tables/collections across any supported backend. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does data_tables accept? +

data_tables accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on data_tables? +

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

What risk level is data_tables? +

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

Can I rate-limit data_tables? +

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

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

data_tables is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

collect_devtools_data on Percepta MCP Server → The MCP Attack Database →

Guides

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