# verify

Verify a 4QUAYS signed message. No API key required. Returns the verified content plus whether the signature is valid and the signer is active — trust the message only when both hold.

Agent View of the PolicyLayer registry record for `verify`. HTML page: https://policylayer.com/tools/4quays-mcp/verify

## Facts

- Tool: `verify`
- Server: 4quays (`@4quays/mcp`) — https://policylayer.com/tools/4quays-mcp.md
- Install: `npx -y @4quays/mcp`
- Homepage: https://www.npmjs.com/package/@4quays/mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | string | no | The message content (only for a detached v1 signature) |
| `signature` | string | no | A detached compact JWS signature |
| `signedMessage` | string | no | A whole 4QUAYS SIGNED MESSAGE block |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "verify",
    "arguments": {}
  }
}
```

## Why verify is rated Low

Even though verify only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Accepts raw HTML/template content (content)

## Use case

AI agents call verify to retrieve information from 4quays without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 4quays:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify": {}
  }
}
```

## Other tools on 4quays (3)

- `decrypt` — Read — https://policylayer.com/tools/4quays-mcp/decrypt.md
- `encrypt_for` — Read — https://policylayer.com/tools/4quays-mcp/encrypt-for.md
- `sign` — Read — https://policylayer.com/tools/4quays-mcp/sign.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=4quays-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4quays-mcp