Low Risk

projectDataExplorer

Query structured project data using natural language (Text-to-SQL). Converts natural language into SQL to retrieve project records, statistics, and aggregations. Pass the user's question as-is without modification. For trade visibility, use siteinsightsAnalyzer instead. WORKFLOW: - Default: call ...

Risk signalsAccepts freeform code/query input (query)

Part of the Cupix Compass server.

projectDataExplorer is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CUPIX COMPASS →

Free to start. No card required.

AI agents call projectDataExplorer 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 projectDataExplorer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "projectDataExplorer": {}
  }
}

See the full Cupix Compass policy for all 6 tools.

Get this rule live on your own Cupix Compass server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CUPIX COMPASS →

These attack patterns abuse exactly the kind of access projectDataExplorer gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so projectDataExplorer only ever does what you allow.

SECURE CUPIX COMPASS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the projectDataExplorer tool do? +

Query structured project data using natural language (Text-to-SQL). Converts natural language into SQL to retrieve project records, statistics, and aggregations. Pass the user's question as-is without modification. For trade visibility, use siteinsightsAnalyzer instead. WORKFLOW: - Default: call this tool with only query. The server resolves team_domain/facility_key from the saved active context (set via setActiveContext). Do NOT call list_teams or list_facilities again just to obtain these values. - Only when the response indicates the context is missing, run list_teams → list_facilities → ask the user → setActiveContext, then retry. - Pass explicit team_domain/facility_key only when the user clearly wants to query a different facility than the saved one. Available tables: - progresses: SI progress metrics (level, category, phase, workarea, cost, dates) - captures: Camera captures metadata (level, camera_model, capture_state, user_email) - records: Capture events with timestamps (captured_at, state, id) - photo_notes: Photonotes (description, state, user_email, created_at) - voice_notes: Voicenotes (level, description, state, user_email, created_at) - facilities: Site info (name, address, size, location, bim_count, created_at) - users: User profiles (name, email) - workareas: Spatial zones (level, name, user_name) Args: query: Natural language question (pass as-is, no SQL syntax) team_domain: Omit by default. Pass only to override the active context. facility_key: Omit by default. Pass only to override the active context. Returns: Query results as tab-separated text. It is categorised as a Read tool in the Cupix Compass MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on projectDataExplorer? +

Register the Cupix Compass MCP server in PolicyLayer and add a rule for projectDataExplorer: 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.

What risk level is projectDataExplorer? +

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

Can I rate-limit projectDataExplorer? +

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

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

projectDataExplorer 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.

Enforce policy on every Cupix Compass tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.