WHEN TO USE: To add one or more monitoring prompts to a project. Prompts are the questions asked to LLMs (e.g.
AI agents use lbm_add_prompts to create or update resources in LLM Brand Monitor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLM Brand Monitor environment.
This tool creates or modifies prompts in the monitoring system, which is a reversible data change. It does not retrieve data (Read), execute arbitrary code (Execute), delete data irreversibly (Destructive), or move money (Financial).
From the tool's definition Tool name 'lbm_add_prompts' and description 'To add one or more monitoring prompts to a project' indicate creation/modification of data (prompts) within a project.
Attacks that exploit this kind of access
WHEN TO USE: To add one or more monitoring prompts to a project. Prompts are the questions asked to LLMs (e.g. It is categorised as a Write tool in the LLM Brand Monitor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LLM Brand Monitor MCP server in PolicyLayer and add a rule for lbm_add_prompts: 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_add_prompts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lbm_add_prompts 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_add_prompts. 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_add_prompts 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 →