validate_integration_manifest
Validate a custom integration manifest against the Adrata safety gates (auth, scopes, rate limits, test endpoint, redaction, idempotency, PII fields, docs URL). Accepts either a file path or an inline manifest object.
This record as markdown: /tools/adrata-starfield-mcp/validate-integration-manifest.md
What validate_integration_manifest does on Starfield
AI agents call validate_integration_manifest 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 |
|---|---|---|---|
path | string | — | Path to adrata.integration.json on disk |
manifest | object | — | Inline manifest JSON; takes precedence over path |
Parameters from the server's own tool schema.
Why validate_integration_manifest is rated Low
Even though validate_integration_manifest 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.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs validate_integration_manifest 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 validate_integration_manifest, this is the rule to start with:
validate_integration_manifest 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 validate_integration_manifest call is checked against it from then on.
Questions about validate_integration_manifest
Validate a custom integration manifest against the Adrata safety gates (auth, scopes, rate limits, test endpoint, redaction, idempotency, PII fields, docs URL). Accepts either a file path or an inline manifest object. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
validate_integration_manifest accepts 2 parameters: path, manifest. 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 validate_integration_manifest: 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.
validate_integration_manifest 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 validate_integration_manifest 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 validate_integration_manifest. 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.
validate_integration_manifest 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