lbm_list_competitors

WHEN TO USE: To see which competitor brands were mentioned by LLMs in responses to this project\

Server LLM Brand Monitor @serpstat/llm-brand-monitor-mcp
Category Read
Risk class Low
Parameters 00 required

What lbm_list_competitors does on LLM Brand Monitor

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

Why lbm_list_competitors needs a policy

This tool retrieves and displays competitor brand mentions from previously completed scans. It queries existing results without modifying, deleting, or executing operations. No irreversible actions or external side effects are possible. Classified as Read with low severity due to limited blast radius—misuse would only expose analysis data already collected.

From the tool's definition Tool name 'lbm_list_competitors' and description 'To see which competitor brands were mentioned by LLMs in responses to this project' indicate data retrieval only. Uses verb 'see' and 'list', which are passive queries with no side effects.

Questions about lbm_list_competitors

What does the lbm_list_competitors tool do? +

WHEN TO USE: To see which competitor brands were mentioned by LLMs in responses to this project\. It is categorised as a Read tool in the LLM Brand Monitor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lbm_list_competitors? +

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

What risk level is lbm_list_competitors? +

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

Can I rate-limit lbm_list_competitors? +

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

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

lbm_list_competitors is provided by the LLM Brand Monitor MCP server (@serpstat/llm-brand-monitor-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.