screen_exclusions
OIG/LEIE federal healthcare exclusion screen — screen a person, business, or 10-digit NPI against the HHS Office of Insp Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/screen-exclusions.md
What screen_exclusions does on GoCreative Agent API
AI agents call screen_exclusions to retrieve information from GoCreative Agent API 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 |
|---|---|---|---|
arg | string | Yes |
Parameters from the server's own tool schema.
Why screen_exclusions is rated Low
Even though screen_exclusions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs screen_exclusions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screen_exclusions, this is the rule to start with:
screen_exclusions 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 GoCreative Agent API, apply this rule, and every screen_exclusions call is checked against it from then on.
Questions about screen_exclusions
OIG/LEIE federal healthcare exclusion screen — screen a person, business, or 10-digit NPI against the HHS Office of Insp Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
screen_exclusions accepts 1 parameter: arg. Required: arg. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for screen_exclusions: 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 GoCreative Agent API. Nothing to install.
screen_exclusions 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 screen_exclusions 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 screen_exclusions. 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.
screen_exclusions is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue