Create a new database in InfluxDB. Database names must follow InfluxDB naming rules: alphanumeric characters, dashes (-), underscores (_), and forward slashes (/) are allowed. Must start with a letter or number. Maximum 64 characters. For Cloud Dedicated, optional configuration parameters can be ...
AI agents use create_database to create or update resources in InfluxDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InfluxDB MCP Server environment.
This tool creates a new database, which is a write operation that modifies infrastructure state. While database creation is reversible (databases can be deleted via the sibling delete_database tool), it has broader blast radius than simple data writes since it affects the entire database structure. Classified as Write rather than Destructive because creation is not irreversible—the database can be removed.
From the tool's definition Tool description explicitly states 'Create a new database' and mentions 'optional configuration parameters can be specified', indicating it creates new data structures with reversible effects.
Attacks that exploit this kind of access
Create a new database in InfluxDB. Database names must follow InfluxDB naming rules: alphanumeric characters, dashes (-), underscores (_), and forward slashes (/) are allowed. Must start with a letter or number. Maximum 64 characters. For Cloud Dedicated, optional configuration parameters can be specified. It is categorised as a Write tool in the InfluxDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InfluxDB MCP Server MCP server in PolicyLayer and add a rule for create_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 InfluxDB MCP Server. Nothing to install.
create_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_database is provided by the InfluxDB MCP Server MCP server (quorralyne/mcp_test_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →