Execute a read-only InfluxQL query against a specific database
AI agents call query 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 time-series data from InfluxDB without modification, deletion, or external execution capabilities. The read-only constraint eliminates Write, Destructive, Execute, and Financial categories. While query tools can sometimes pose risks if they permit resource exhaustion or information disclosure, the read-only nature and JWT authentication mitigate misuse potential.
From the tool's definition Tool description states 'read-only' query execution. Server description emphasizes 'read-only access to time-series data'. The query capability is explicitly constrained to retrieve data without side effects.
Attacks that exploit this kind of access
Execute a read-only InfluxQL query against a specific database. 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 query: 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.
query 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 query 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 query. 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.
query is provided by the InfluxDB MCP Server MCP server (m4tyn0/influx_mcp). 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 →