Create a new InfluxDB named admin token with full administrative permissions (Core/Enterprise only). Named admin tokens can manage databases, users, and resource tokens, but cannot manage other admin tokens.
AI agents use create_admin_token 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 admin token, which is a Write operation (creating a new resource). However, the severity is high because admin tokens grant full administrative permissions to manage databases, users, and resource tokens — misuse could lead to privilege escalation or unauthorized access to the entire InfluxDB instance.
From the tool's definition 'Create a new InfluxDB named admin token with full administrative permissions' — creates a new persistent credential with broad administrative access
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Create a new InfluxDB named admin token with full administrative permissions (Core/Enterprise only). Named admin tokens can manage databases, users, and resource tokens, but cannot manage other admin tokens. 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_admin_token: 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_admin_token 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_admin_token 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_admin_token. 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_admin_token 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 →