# get_company

Fetch one full Agent Papers company entry including offerings, sources, freshness, and category-specific facts.

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

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes | Company slug, for example agentcall. |

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

## Why get_company is rated Low

This tool reads and returns company registry data without side effects. While the registry contains sensitive information (identity, phone, email, addresses, money, legal, insurance data), the tool itself only retrieves existing records—it does not modify, delete, or execute actions.

From the tool's own definition: "Tool performs a fetch/retrieval action: 'Fetch one full Agent Papers company entry'. The description indicates it retrieves data (company entry, offerings, sources, freshness, facts) with no modification, deletion, or execution of external operations."

## Use case

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

## Other tools on Agent Papers (5)

- `compare` — Read — https://policylayer.com/tools/dev-agentpapers-agent-papers/compare.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
- `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