health.supplements.details
Get full supplement label data — ingredients, amounts per serving, daily values, target groups (NIH DSLD)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/health.supplements.details.md
What health.supplements.details does on Apibase
AI agents call health.supplements.details 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 |
|---|---|---|---|
dsld_id | integer | Yes | NIH DSLD supplement label ID |
Parameters from the server's own tool schema.
Why health.supplements.details is rated Low
Tool retrieves publicly available supplement information without modifying data or triggering external operations.
From the tool's definition Get full supplement label data — ingredients, amounts per serving, daily values
Attacks that exploit this kind of access
The rule that runs health.supplements.details 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 health.supplements.details, this is the rule to start with:
health.supplements.details 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 health.supplements.details call is checked against it from then on.
Questions about health.supplements.details
Get full supplement label data — ingredients, amounts per serving, daily values, target groups (NIH DSLD). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
health.supplements.details accepts 1 parameter: dsld_id. Required: dsld_id. 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 health.supplements.details: 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.
health.supplements.details 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 health.supplements.details 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 health.supplements.details. 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.
health.supplements.details 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