WHEN TO USE: To get full details of a specific brand monitoring project including all prompts.
AI agents call lbm_get_project 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.
This tool retrieves and returns information about a brand monitoring project. There are no side effects, data modifications, deletions, code execution, or financial operations. It is a straightforward read operation that fetches project details.
From the tool's definition Tool name 'lbm_get_project' and description 'To get full details of a specific brand monitoring project including all prompts' indicates retrieval/query of existing project data with no modification.
Attacks that exploit this kind of access
WHEN TO USE: To get full details of a specific brand monitoring project including all prompts. It is categorised as a Read tool in the LLM Brand Monitor MCP Server, which means it retrieves data without modifying state.
Register the LLM Brand Monitor MCP server in PolicyLayer and add a rule for lbm_get_project: 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.
lbm_get_project 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 lbm_get_project 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 lbm_get_project. 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.
lbm_get_project 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.
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 →