use_database

THE RISK

Medium Risk

Why use_database needs a policy

This tool changes the session state (active database context) which is a stateful modification, but it doesn't create, delete, or irreversibly alter data. It's more than a read since it changes session configuration, making Write the appropriate category. The blast radius is low as it only affects subsequent queries in the session.

From the tool's definition Switch the current database context for subsequent queries

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

POLICY

How to control use_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 use_database:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "use_database": {
      "limits": [
        {
          "counter": "use_database_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

use_database stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.

LIMIT 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 Read current_database Get the current database context being used for 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about use_database

What does the use_database tool do? +

Switch the current database context for subsequent queries. It is categorised as a Write tool in the Treasure Data MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on use_database? +

Register the Treasure Data MCP Server MCP server in PolicyLayer and add a rule for use_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 use_database? +

use_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit use_database? +

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

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

use_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 →