database · Zion MCP: Risk & Policy

WHAT IT DOES

What database does on Zion

AI agents use database to create or update resources in Zion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zion environment.

PARAMETERS

Parameter	Type	Required
`op`	string	Yes
`args`	object	—
`appExId`	string \| null	—
`projectExId`	string	—
`appVersionExId`	string \| null	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why database needs a policy

This tool modifies data structures reversibly (tables, columns, relations, constraints) but does not permanently delete data or schemas. Schema edits can be undone or corrected, making it Write rather than Destructive.

From the tool's definition Tool description states 'Edit the data model — tables, columns, relations, unique constraints, display names' with operations that modify database schema structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

database Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zion, so you can run agents against it safely.

FAQ

Questions about database

What does the database tool do? +

Edit the data model — tables, columns, relations, unique constraints, display names. op is a schema ToolName from the enum; args is its payload. Call guide {plugin:"database"} first for the rules and per-op arg shapes. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does database accept? +

database accepts 5 parameters: op, args, appExId, projectExId, appVersionExId. Required: op. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on database? +

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

What risk level is database? +

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

Can I rate-limit database? +

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

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

database is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.