# get_pattern

Get the full accessibility specification for one pattern by id (ids come from list_patterns). Returns the pattern's sections: must_haves (non-negotiable WCAG 2.2 AA requirements — implement all of them), donts (anti-patterns — never produce), golden_pattern (a reference implementation to model), and customizable (allowed variations). Call this for each pattern you selected before writing UI code.

Agent View of the PolicyLayer registry record for `get_pattern`. HTML page: https://policylayer.com/tools/a11y-context-mcp-server/get-pattern

## Facts

- Tool: `get_pattern`
- Server: A11y Context (`@a11y-context/mcp-server`) — https://policylayer.com/tools/a11y-context-mcp-server.md
- Install: `npx -y @a11y-context/mcp-server`
- Homepage: https://www.npmjs.com/package/@a11y-context/mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes |  |
| `stack` | string | no | Target platform and framework. Defaults to 'web/react'. A stack is available only if this release bundles content for it; 'android/compose' is reserved and not |

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": "get_pattern",
    "arguments": {
      "id": "<id>"
    }
  }
}
```

## Why get_pattern is rated Low

Even though get_pattern 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.

## Use case

AI agents call get_pattern to retrieve information from A11y Context 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 A11y Context:

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

## Other tools on A11y Context (2)

- `get_foundations` — Read — https://policylayer.com/tools/a11y-context-mcp-server/get-foundations.md
- `list_patterns` — Read — https://policylayer.com/tools/a11y-context-mcp-server/list-patterns.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=a11y-context-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a11y-context-mcp-server