lexq_webhook_subscriptions_list

List platform event webhook subscriptions. These receive deployment lifecycle notifications (publish, deploy, rollback, undeploy).

Server LexQ lexq-io/lexq-cli
Category Read
Risk class Low
Parameters 00 required

What lexq_webhook_subscriptions_list does on LexQ

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

Why lexq_webhook_subscriptions_list needs a policy

This is a read-only operation that retrieves information about webhook subscriptions. It has no side effects, does not modify data, and does not execute external actions. The low severity reflects that exposure of this tool to an AI agent would only allow querying subscription metadata, with minimal blast radius unless the information itself is sensitive business intelligence.

From the tool's definition Tool name contains 'list' and description states 'List platform event webhook subscriptions' — retrieves subscription data with no modification capability. It queries existing webhook subscriptions that receive notifications about deployment events.

Questions about lexq_webhook_subscriptions_list

What does the lexq_webhook_subscriptions_list tool do? +

List platform event webhook subscriptions. These receive deployment lifecycle notifications (publish, deploy, rollback, undeploy). It is categorised as a Read tool in the LexQ MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lexq_webhook_subscriptions_list? +

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

What risk level is lexq_webhook_subscriptions_list? +

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

Can I rate-limit lexq_webhook_subscriptions_list? +

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

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

lexq_webhook_subscriptions_list is provided by the LexQ MCP server (lexq-io/lexq-cli). 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.