List construction facilities (projects) the user can access within a team. Use this tool ONLY when the user wants to switch facility or has no saved active context. If getActiveContext returns a saved facility_key, do NOT call this tool — call the analysis tool directly with no arguments. Require...
Part of the Cupix Compass server.
Free to start. No card required.
AI agents call listFacilities to retrieve information from Cupix Compass without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though listFacilities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"listFacilities": {}
}
}See the full Cupix Compass policy for all 6 tools.
These attack patterns abuse exactly the kind of access listFacilities gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List construction facilities (projects) the user can access within a team. Use this tool ONLY when the user wants to switch facility or has no saved active context. If getActiveContext returns a saved facility_key, do NOT call this tool — call the analysis tool directly with no arguments. Required workflow when this tool IS appropriate: 1. Present the returned facilities to the user. 2. Wait for the user to select one. 3. Call setActiveContext(team_domain, facility_key) to persist the selection so future sessions skip this step. 4. Then invoke analysis tools. Args: team_domain: Team domain returned by list_teams(). Optional; if omitted, falls back to the setActiveContext-saved value, otherwise returns the team list. Returns: str: Accessible facilities with their keys and names.. It is categorised as a Read tool in the Cupix Compass MCP Server, which means it retrieves data without modifying state.
Register the Cupix Compass MCP server in PolicyLayer and add a rule for listFacilities: 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 Cupix Compass. Nothing to install.
listFacilities 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 listFacilities 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 listFacilities. 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.
listFacilities is provided by the Cupix Compass MCP server (https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Cupix Compass tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.