Get a list of all measurements (tables) in a database (all versions). Uses the InfluxDB information_schema.columns to discover tables.
AI agents call get_measurements 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 schema metadata from InfluxDB without modifying, executing, or deleting anything. It is a pure query/discovery operation analogous to SHOW TABLES or querying system catalogs, which are classified as Read operations.
From the tool's definition Tool description explicitly states 'Get a list of all measurements (tables)' and 'discover tables' using information_schema.columns—a read-only introspection operation with no side effects.
Attacks that exploit this kind of access
Get a list of all measurements (tables) in a database (all versions). Uses the InfluxDB information_schema.columns to discover tables. 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 get_measurements: 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.
get_measurements 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 get_measurements 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 get_measurements. 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.
get_measurements 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 →