pendo_get_feature_usage

Query Pendo for feature usage analytics (click events, unique visitors) over a time range. Useful for understanding how heavily a feature is used when reviewing feedback threads.

Server Yocoolab yocoolab/mcp-server
Category Read
Risk class Low
Parameters 00 required

What pendo_get_feature_usage does on Yocoolab

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

Why pendo_get_feature_usage needs a policy

This tool queries analytics data (click events, unique visitors) from Pendo over a specified time range. It is a read-only operation that retrieves information without side effects. There is no data modification, deletion, code execution, or financial impact. The tool fits squarely in the Read category for data retrieval and analysis.

From the tool's definition 'Query Pendo for feature usage analytics (click events, unique visitors) over a time range' - the tool retrieves analytics data without modifying, deleting, or executing any operations.

Questions about pendo_get_feature_usage

What does the pendo_get_feature_usage tool do? +

Query Pendo for feature usage analytics (click events, unique visitors) over a time range. Useful for understanding how heavily a feature is used when reviewing feedback threads. It is categorised as a Read tool in the Yocoolab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pendo_get_feature_usage? +

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

What risk level is pendo_get_feature_usage? +

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

Can I rate-limit pendo_get_feature_usage? +

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

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

pendo_get_feature_usage is provided by the Yocoolab MCP server (yocoolab/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

pendo_get_feature_usage is one line of Yocoolab'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.