Get details of a specific database token by ID for InfluxDB Cloud-Dedicated cluster.
AI agents call cloud_get_database_token to retrieve information from InfluxDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries token metadata for a specific database token in InfluxDB Cloud-Dedicated. It performs a read-only lookup operation with no side effects. While token metadata could be considered sensitive information, the tool itself only retrieves existing data without creating, modifying, or deleting it.
From the tool's definition Tool name includes 'get' and description states 'Get details of a specific database token by ID' — this is a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get details of a specific database token by ID for InfluxDB Cloud-Dedicated cluster. It is categorised as a Read tool in the InfluxDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the InfluxDB MCP Server MCP server in PolicyLayer and add a rule for cloud_get_database_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.
cloud_get_database_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cloud_get_database_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 cloud_get_database_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.
cloud_get_database_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 →