// SCAN REPORT

Quire MCP Server

61 tools. 31 can modify or destroy data without limits.

8 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

31 can modify or destroy data

30 read-only

61 tools total

Community server · catalogue entry verified 29/06/2026

How to control Quire MCP Server ↓

TOOL MAP

What Quire MCP Server exposes to your agents

Read (30) Write / Execute (23) Destructive / Financial (8)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Quire MCP Server tools

Destructive · High quire.deleteChat The tool permanently removes a chat channel with no recovery option. Destructive · High quire.deleteComment Deletion of comments is an irreversible operation with no undo capability. Destructive · High quire.deleteDocument The tool explicitly deletes a document and states the action is irreversible, which is the defining characteristic of the Destructive category. Destructive · High quire.deleteStorageValue This tool permanently removes stored data without any possibility of recovery or reversal.

31 of Quire MCP Server's 61 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Quire MCP Server

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

Deny destructive operations

{
  "quire.deleteChat": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "quire.addChatComment": {
    "limits": [
      {
        "counter": "quire.addchatcomment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "quire.exportProject": {
    "limits": [
      {
        "counter": "quire.exportproject_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 Quire MCP Server — 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 QUIRE →

Instant setup, no code required.

FULL CATALOGUE

All 61 Quire MCP Server tools

DESTRUCTIVE 8 tools

Destructive quire.deleteChat Delete a chat channel by OID, or by owner type/ID and chat ID. This action cannot be undone. Destructive quire.deleteComment Delete a comment. This action cannot be undone. Destructive quire.deleteDocument Delete a document by OID, or by owner type/ID and document ID. This action cannot be undone. Destructive quire.deleteStatus Delete a custom status. Tasks with this status will be reverted to Destructive quire.deleteStorageValue Delete a stored value by name. This action cannot be undone. Destructive quire.deleteSublist Delete a sublist by OID, or by owner type/ID and sublist ID. This action cannot be undone. Destructive quire.deleteTag Delete a tag. This will remove the tag from all tasks that have it. Destructive quire.deleteTask Delete a task and all its subtasks. This action cannot be undone.

WRITE 23 tools

Write quire.addChatComment Add a comment to a chat channel by OID, or by project ID and chat ID. Write quire.addTaskComment Add a comment to a task. Can be accessed by task OID Write quire.createChat Create a new chat channel in a project. Write quire.createDocument Create a new document in an organization or project. Write quire.createStatus Create a custom status in a project. Custom statuses allow you to Write quire.createSublist Create a new sublist in an organization, project, folder, or smart-folder. Write quire.createTag Create a new tag in a project. Tags help organize and categorize tasks. Write quire.createTask Create a new task in a project or as a subtask of an existing task. Write quire.createTaskAfter Create a new task immediately after a specified task. Write quire.createTaskBefore Create a new task immediately before a specified task. Write quire.putStorageValue Store a value in Quire Write quire.sendNotification Send a notification to the current authorized user. Write quire.updateChat Update a chat channel Write quire.updateComment Update an existing comment Write quire.updateDocument Update a document Write quire.updateOrganization Update an organization Write quire.updateProject Update a project Write quire.updateStatus Update a custom status Write quire.updateSublist Update a sublist Write quire.updateTag Update a tag Write quire.updateTask Update an existing task. Can be identified by project ID + task ID, Write quire.uploadCommentAttachment Upload a file attachment to a comment. Write quire.uploadTaskAttachment Upload a file attachment to a task.

READ 30 tools

Read quire.exportProject Export all tasks from a project in JSON or CSV format. Read quire.getChat Get a chat channel by OID, or by owner type/ID and chat ID. Read quire.getDocument Get a document by OID, or by owner type/ID and document ID. Read quire.getOrganization Get detailed information about a specific organization by its ID or OID. Read quire.getPartner Get details of an external team (partner) by OID. Read quire.getProject Get detailed information about a specific project by its ID or OID. Read quire.getStatus Get detailed information about a specific custom status by its value. Read quire.getStorageValue Get a stored value by name from Quire Read quire.getSublist Get a sublist by OID, or by owner type/ID and sublist ID. Read quire.getTag Get detailed information about a specific tag by its OID. Read quire.getTask Get detailed information about a specific task. Read quire.getUser Get detailed information about a user by their ID, OID, or email. Read quire.listChatComments List all comments on a chat channel by OID, or by project ID and chat ID. Read quire.listChats List all chat channels in a project. Read quire.listDocuments List all documents in an organization, project, folder, or smart-folder. Read quire.listOrganizations List all organizations accessible to the current user. Read quire.listPartners List all external teams (partners) in a project. Read quire.listProjectMembers List all members of a project. Read quire.listProjects List all projects accessible to the current user. Read quire.listStatuses List all custom statuses in a project. Returns an array of status objects Read quire.listStorageEntries List all storage entries with a given prefix. Read quire.listSublists List all sublists in an organization, project, folder, or smart-folder. Read quire.listTaskComments List all comments on a task. Can be accessed by task OID Read quire.listTasks List tasks in a project. Returns root-level tasks by default, Read quire.listUsers List all users accessible to the current user. Read quire.searchFolderTasks Search for tasks within a specific folder by keyword and optional filters. Read quire.searchOrganizationTasks Search for tasks across an entire organization by keyword and optional filters. Read quire.searchTasks Search for tasks in a project by keyword and optional filters. Read quire.whoami Get the current authenticated user

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Quire MCP Server

Can an AI agent delete data through the Quire MCP Server MCP server? +

Yes. The Quire MCP Server server exposes 8 destructive tools including quire.deleteChat, quire.deleteComment, quire.deleteDocument. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Quire MCP Server? +

The Quire MCP Server server has 23 write tools including quire.addChatComment, quire.addTaskComment, quire.createChat. 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 Quire MCP Server.

How many tools does the Quire MCP Server MCP server expose? +

61 tools across 3 categories: Destructive, Read, Write. 30 are read-only. 31 can modify, create, or delete data.

How do I enforce a policy on Quire MCP Server? +

Register the Quire MCP Server 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 Quire MCP Server tool call.

Deterministic rules across all 61 Quire MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON QUIRE →

Instant setup, no code required.

61 Quire MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.