Low Risk

virt_get_schemas

Retrieve and return a list of all schema names from the connected Virtuoso database.

How to control virt_get_schemas ↓

What virt_get_schemas does on Mcp Odbc

AI agents call virt_get_schemas to retrieve information from Mcp Odbc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why virt_get_schemas needs a policy

This tool retrieves metadata (schema names) from a Virtuoso database without side effects. It is purely informational and does not create, modify, delete, or execute operations. The blast radius of misuse is minimal — an attacker gains only schema enumeration capability, which is typically low-risk reconnaissance information.

From the tool's definition Tool description states it 'Retrieve and return a list of all schema names' — a read-only query operation with no data modification, deletion, or execution of arbitrary code.

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

How to control virt_get_schemas

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Odbc, and nothing reaches the server without passing your rules. This is the rule we recommend for virt_get_schemas:

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

virt_get_schemas 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 Odbc — 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.

Related tools and policies

Go deeper

Questions about virt_get_schemas

What does the virt_get_schemas tool do? +

Retrieve and return a list of all schema names from the connected Virtuoso database. It is categorised as a Read tool in the Mcp Odbc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on virt_get_schemas? +

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

What risk level is virt_get_schemas? +

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

Can I rate-limit virt_get_schemas? +

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

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

virt_get_schemas is provided by the Mcp Odbc MCP server (openlinksoftware/mcp-odbc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Odbc tool call.

Start from Mcp Odbc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 Mcp Odbc tools catalogued and risk-classified — across an index of 43,000+ 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.