// SCAN REPORT

Inquira

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 12 Aug 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry checked 05/08/2026 · full schemas captured for 6 of 6 tools

How to control Inquira ↓

TOOL MAP

What Inquira exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Inquira costs in tokens

420 tokens of tool definitions, loaded on every request

0.2% of a 200k context window

133 heaviest tool: create_survey

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Inquira tools

Write · Medium create_survey This tool creates new survey data, which is a Write operation—data is generated and persisted but remains modifiable and deletable. Write · Medium publish_survey Publishing a survey modifies its state from draft/hidden to publicly accessible, which is a reversible write operation.

2 of Inquira's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Inquira

PolicyLayer is an MCP gateway — it sits between your AI agents and Inquira, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_survey": {
    "limits": [
      {
        "counter": "create_survey_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_ai_report": {
    "limits": [
      {
        "counter": "get_ai_report_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Inquira — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON INQUIRA →

Instant setup, no code required.

FULL CATALOGUE

All 6 Inquira tools

WRITE 2 tools

Write create_survey Generate a professional survey using AI based on a research goal. Returns the survey ID and shareable link. Write publish_survey Publish a survey to make it accessible via its share link.

READ 4 tools

Read get_ai_report Generate an AI analysis report for a survey's responses. Returns executive summary, key metrics, per-question Read get_responses Get all responses submitted to a specific survey. Read get_survey_link Get the shareable link for a published survey. Read get_surveys List all surveys belonging to the authenticated user.

FAQ

Questions about Inquira

How do I prevent bulk modifications through Inquira? +

The Inquira server has 2 write tools including create_survey, publish_survey. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Inquira.

How many tools does the Inquira MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Inquira? +

Register the Inquira MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Inquira tool call.

Deterministic rules across all 6 Inquira tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON INQUIRA →

Instant setup, no code required.

6 Inquira tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Inquira's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →