get_company
Fetch one full Agent Papers company entry including offerings, sources, freshness, and category-specific facts.
This record as markdown: /tools/dev-agentpapers-agent-papers/get-company.md
What get_company does on Agent Papers
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Company slug, for example agentcall. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_company safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Papers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_company, this is the rule to start with:
get_company is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Papers, apply this rule, and every get_company call is checked against it from then on.
Questions about get_company
Fetch one full Agent Papers company entry including offerings, sources, freshness, and category-specific facts. It is categorised as a Read tool in the Agent Papers MCP Server, which means it retrieves data without modifying state.
get_company accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Papers MCP server in PolicyLayer and add a rule for get_company: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent Papers. Nothing to install.
get_company is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_company rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_company. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_company is provided by the Agent Papers MCP server (https://agentpapers.dev/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Papers, and thousands of servers like it.
This server
Across the catalogue