sam.gov.entity_detail
Get full SAM.gov registration details for a federal contractor by UEI (Unique Entity Identifier). Returns legal name, CAGE code, addresses, NAICS/PSC codes, business certifications, entity structure, organization type, and registration dates. Source: SAM.gov (GSA).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sam.gov.entity-detail.md
What sam.gov.entity_detail does on Apibase
AI agents call sam.gov.entity_detail to retrieve information from Apibase 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 |
|---|---|---|---|
uei | string | Yes | Unique Entity Identifier (UEI) — 12-character SAM.gov ID (e.g. KM99JJBNQ9M5 for Lockheed Martin) |
Parameters from the server's own tool schema.
Why sam.gov.entity_detail is rated Low
Queries publicly available federal contractor registration data without modifying, executing, or deleting information.
From the tool's definition Get full SAM.gov registration details for a federal contractor by UEI. Returns legal name, CAGE code, addresses, NAICS/PSC codes, business certifications, entity structure, organization type, and registration dates.
Attacks that exploit this kind of access
The rule that runs sam.gov.entity_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sam.gov.entity_detail, this is the rule to start with:
sam.gov.entity_detail 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 Apibase, apply this rule, and every sam.gov.entity_detail call is checked against it from then on.
Questions about sam.gov.entity_detail
Get full SAM.gov registration details for a federal contractor by UEI (Unique Entity Identifier). Returns legal name, CAGE code, addresses, NAICS/PSC codes, business certifications, entity structure, organization type, and registration dates. Source: SAM.gov (GSA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sam.gov.entity_detail accepts 1 parameter: uei. Required: uei. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for sam.gov.entity_detail: 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 Apibase. Nothing to install.
sam.gov.entity_detail 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 sam.gov.entity_detail 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 sam.gov.entity_detail. 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.
sam.gov.entity_detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue