test_provider_credential
Run a policy/audit-mapped credential test for a provider. Defaults to dry-run so Claude Code can check shape and policy before touching live credentials.
This record as markdown: /tools/adrata-starfield-mcp/test-provider-credential.md
What test_provider_credential does on Starfield
AI agents call test_provider_credential to retrieve information from Starfield 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 |
|---|---|---|---|
dryRun | boolean | — | Defaults to true. Set false only for an authenticated live credential test. |
manifest | object | — | Inline custom integration manifest for local/provider test planning |
provider | string | Yes | Provider slug |
credentialRef | string | — | Stored credential reference to test |
Parameters from the server's own tool schema.
Why test_provider_credential is rated Low
Even though test_provider_credential 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 test_provider_credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_provider_credential, this is the rule to start with:
test_provider_credential 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 Starfield, apply this rule, and every test_provider_credential call is checked against it from then on.
Questions about test_provider_credential
Run a policy/audit-mapped credential test for a provider. Defaults to dry-run so Claude Code can check shape and policy before touching live credentials. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
test_provider_credential accepts 4 parameters: dryRun, manifest, provider, credentialRef. Required: provider. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for test_provider_credential: 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 Starfield. Nothing to install.
test_provider_credential 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 test_provider_credential 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 test_provider_credential. 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.
test_provider_credential is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue