current_database

THE RISK

Low Risk

Why current_database needs a policy

This tool retrieves information about the current database context without modifying, deleting, or executing operations. It is purely informational and poses minimal security risk—an AI agent misusing it could at worst learn which database is in scope, which is low-impact information disclosure.

From the tool's definition Tool name 'current_database' and description 'Get the current database context being used for queries' indicate a retrieval operation with no side effects.

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

POLICY

How to control current_database

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

policy.json

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

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

Create a free account and register Treasure Data MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Treasure Data MCP Server tools

Destructive execute Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true Destructive kill_attempt Request cancellation of a running attempt Execute retry_attempt Retry a specific failed attempt with resume capabilities Execute retry_session Retry a failed session from the beginning or a specific task Write use_database Switch the current database context for subsequent queries Read describe_table Get column information for a specific table Read get_attempt_tasks List all tasks within an attempt with their execution status Read get_parent_segment [EXPERIMENTAL] Get details of a specific parent segment by its ID. Requires parent_segment

All 23 Treasure Data MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about current_database

What does the current_database tool do? +

Get the current database context being used for queries. It is categorised as a Read tool in the Treasure Data MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on current_database? +

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

What risk level is current_database? +

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

Can I rate-limit current_database? +

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

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

current_database is provided by the Treasure Data MCP Server MCP server (treasure-data/td-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Treasure Data MCP Server tool call.

Start from Treasure Data MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →