quire.sendNotification · Quire MCP Server MCP: Risk & Policy

WHAT IT DOES

What quire.sendNotification does on Quire MCP Server

AI agents use quire.sendNotification to create or update resources in Quire MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Quire MCP Server environment.

WHY IT NEEDS A POLICY

Why quire.sendNotification needs a policy

This tool creates a notification artifact (write operation) with reversible effects. While notifications are not critical data modifications compared to other tools in the sibling set (like createTask, createDocument), the tool could be misused to spam notifications or send misleading information to users, affecting their workflow.

From the tool's definition The tool description states it can 'Send a notification to the current authorized user', which is a write operation that creates/modifies notification state in the Quire system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quire.sendNotification Rate-limited

quire.sendNotification stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "quire.sendNotification": {
      "limits": [
        {
          "counter": "quire.sendnotification_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Quire MCP Server, so you can run agents against it safely.

FAQ

Questions about quire.sendNotification

What does the quire.sendNotification tool do? +

Send a notification to the current authorized user. It is categorised as a Write tool in the Quire MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on quire.sendNotification? +

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

What risk level is quire.sendNotification? +

quire.sendNotification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit quire.sendNotification? +

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

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

quire.sendNotification is provided by the Quire MCP Server MCP server (jacob-hartmann/quire-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.