parse_filter_expression

Convert a plain-text filter expression into a GA4 API filterExpression object. e.g., input:

Server Query Analytics josephtandle/google-analytics-mcp-mcp
Category Read
Risk class Low
Parameters 00 required

What parse_filter_expression does on Query Analytics

AI agents call parse_filter_expression to retrieve information from Query Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why parse_filter_expression needs a policy

The tool takes a plain-text filter expression and converts it into a structured GA4 API object. This is a local parsing/transformation operation that reads input and produces output without querying external systems, modifying data, or triggering any external operations. It is a utility function that eliminates manual GA4 API syntax construction, consistent with the server's stated purpose.

From the tool's definition 'Convert a plain-text filter expression into a GA4 API filterExpression object' — this is a pure transformation/parsing operation with no side effects

Questions about parse_filter_expression

What does the parse_filter_expression tool do? +

Convert a plain-text filter expression into a GA4 API filterExpression object. e.g., input:. It is categorised as a Read tool in the Query Analytics MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on parse_filter_expression? +

Register the Query Analytics MCP server in PolicyLayer and add a rule for parse_filter_expression: 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 Query Analytics. Nothing to install.

What risk level is parse_filter_expression? +

parse_filter_expression is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit parse_filter_expression? +

Yes. Add a rate_limit block to the parse_filter_expression 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.

How do I block parse_filter_expression completely? +

Set action: deny in the PolicyLayer policy for parse_filter_expression. 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.

What MCP server provides parse_filter_expression? +

parse_filter_expression is provided by the Query Analytics MCP server (josephtandle/google-analytics-mcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

parse_filter_expression is one line of Query Analytics's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.