# search

Search Agent Papers companies by name or tagline, optionally constrained by category and status. Returns compact vendor records for ranking.

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

## Facts

- Tool: `search`
- 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: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `query` | string | yes | Substring to match against company name and tagline. |
| `status` | string | no | Optional company or offering status filter. |
| `category` | string | no | Optional category filter. |

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

## Why search is rated Low

The tool performs a query/search operation characteristic of Read category tools. It retrieves and returns data without creating, modifying, or deleting records. The elevated severity (medium vs. low) reflects that the underlying data is highly sensitive personal and financial information about companies; unrestricted search access could enable reconnaissance for social engineering, targeting, or fraud schemes.

From the tool's own definition: "Tool description states it 'Search Agent Papers companies by name or tagline' and 'Returns compact vendor records for ranking' — pure retrieval operation with no modification or deletion."

## Use case

AI agents call search 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": {
    "search": {}
  }
}
```

## 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
- `get_schema` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/get-schema.md
- `list_categories` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/list-categories.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