list_outlets

List shop outlets/locations for the company.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/list-outlets.md

WHAT IT DOES

What list_outlets does on FavCRM

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

Parameter	Type	Required	Description
`activeOnly`	boolean	—	When true, only return active outlets (default false)

Parameters from the server's own tool schema.

RISK

Why list_outlets is rated Low

This tool retrieves and queries outlet/location data without side effects. It performs a simple data retrieval operation typical of CRM systems, with minimal blast radius if misused by an AI agent. No data is modified, deleted, or financial transactions are involved.

From the tool's definition Tool name 'list_outlets' and description 'List shop outlets/locations for the company' indicate a retrieval operation with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_outlets safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_outlets, this is the rule to start with:

list_outlets Allowed

list_outlets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_outlets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every list_outlets call is checked against it from then on.

FAQ

Questions about list_outlets

What does the list_outlets tool do? +

List shop outlets/locations for the company. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.

What parameters does list_outlets accept? +

list_outlets accepts 1 parameter: activeOnly. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_outlets? +

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

What risk level is list_outlets? +

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

Can I rate-limit list_outlets? +

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

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

list_outlets is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →