AI agents call pendo_list_guides 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.
This tool retrieves and filters existing Pendo guide data without creating, modifying, deleting, or executing any operations. It is purely informational/observational in nature. The blast radius of misuse is minimal - an attacker could only view what guides are deployed, not modify or delete them. Severity is low as this exposes marketing/help content that is typically non-sensitive.
From the tool's definition Tool description states 'List active in-app guides from Pendo. Optionally filter by page URL' - the verb 'list' and 'filter' indicate read-only querying operations with no side effects.
Attacks that exploit this kind of access
List active in-app guides from Pendo. Optionally filter by page URL to see what guides are deployed on a specific page. It is categorised as a Read tool in the Yocoolab MCP Server, which means it retrieves data without modifying state.
Register the Yocoolab MCP server in PolicyLayer and add a rule for pendo_list_guides: 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.
pendo_list_guides 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 pendo_list_guides 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 pendo_list_guides. 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.
pendo_list_guides 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.
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 →