# get_schema

Return field names and plain-English buyer reasons for the full registry schema or one category.

Agent View of the PolicyLayer registry record for `get_schema`. HTML page: https://policylayer.com/tools/dev-agentpapers-agent-papers/get-schema

## Facts

- Tool: `get_schema`
- Server: Agent Papers (`https://agentpapers.dev/api/mcp`) — https://policylayer.com/tools/dev-agentpapers-agent-papers.md
- Homepage: https://github.com/https://agentpapers.dev/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `category` | string | no | Optional category id. |

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

## Why get_schema is rated Low

This tool queries and returns informational schema metadata about the registry structure. It retrieves data without side effects—no data is created, modified, deleted, or executed. The action is purely informational retrieval, fitting the Read category. Severity is low because schema disclosure poses minimal immediate risk; it exposes structure rather than sensitive instance data or operational capabilities.

From the tool's own definition: "Tool name 'get_schema' and description 'Return field names and plain-English buyer reasons' indicates retrieval of metadata/schema information only, with no modification, deletion, or execution of external operations."

## Use case

AI agents call get_schema to retrieve information from Agent Papers 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 Agent Papers:

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

## Other tools on Agent Papers (5)

- `compare` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/compare.md
- `get_company` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/get-company.md
- `list_categories` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/list-categories.md
- `search` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/search.md
- `whats_new` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/whats-new.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=dev-agentpapers-agent-papers · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agentpapers-agent-papers