Retrieve a list of all families for a given brand.
AI agents call list_families to retrieve information from WatchBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structured data from the WatchBase database (family listings for a brand) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects, making it the lowest risk category. The severity is low because querying a public database carries minimal risk of misuse.
From the tool's definition Tool name 'list_families' and description 'Retrieve a list of all families for a given brand' indicate querying/retrieval of data with no modification or execution of operations.
Attacks that exploit this kind of access
Retrieve a list of all families for a given brand. It is categorised as a Read tool in the WatchBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WatchBase MCP Server MCP server in PolicyLayer and add a rule for list_families: 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 WatchBase MCP Server. Nothing to install.
list_families 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 list_families 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 list_families. 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.
list_families is provided by the WatchBase MCP Server MCP server (watchdealer-pavel/watchbase-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 →