get_segment_metrics

Get ranking performance metrics broken down by user segment — useful for understanding how different user groups respond to your ranking configuration.

Server NeuronSearchLab neuronsearchlab/mcp
Category Read
Risk class Low
Parameters 00 required

What get_segment_metrics does on NeuronSearchLab

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

Why get_segment_metrics needs a policy

This tool retrieves and queries performance metrics grouped by user segments. The verb 'Get' combined with the read-only nature of accessing pre-computed metrics for analysis purposes clearly categorizes this as a Read operation. There is no data modification, deletion, execution of external operations, or financial impact.

From the tool's definition Tool name 'get_segment_metrics' and description 'Get ranking performance metrics broken down by user segment' indicate retrieval of analytical data with no modification or side effects.

Questions about get_segment_metrics

What does the get_segment_metrics tool do? +

Get ranking performance metrics broken down by user segment — useful for understanding how different user groups respond to your ranking configuration. It is categorised as a Read tool in the NeuronSearchLab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_segment_metrics? +

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

What risk level is get_segment_metrics? +

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

Can I rate-limit get_segment_metrics? +

Yes. Add a rate_limit block to the get_segment_metrics 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 get_segment_metrics completely? +

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

get_segment_metrics is provided by the NeuronSearchLab MCP server (neuronsearchlab/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.