Low Risk

describe_skin_types

Returns the six Fitzpatrick skin types with sun-reactivity behavior and descriptive ancestry hints. Call this when the user's skin type is unknown so you can pick the closest match before calling calculate.

Part of the D Fetcher server.

describe_skin_types is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE D FETCHER →

Free to start. No card required.

AI agents call describe_skin_types to retrieve information from D Fetcher without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though describe_skin_types only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_skin_types": {}
  }
}

See the full D Fetcher policy for all 3 tools.

Get this rule live on your own D Fetcher server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY D FETCHER →

These attack patterns abuse exactly the kind of access describe_skin_types gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so describe_skin_types only ever does what you allow.

SECURE D FETCHER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the describe_skin_types tool do? +

Returns the six Fitzpatrick skin types with sun-reactivity behavior and descriptive ancestry hints. Call this when the user's skin type is unknown so you can pick the closest match before calling calculate.. It is categorised as a Read tool in the D Fetcher MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_skin_types? +

Register the D Fetcher MCP server in PolicyLayer and add a rule for describe_skin_types: 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 D Fetcher. Nothing to install.

What risk level is describe_skin_types? +

describe_skin_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit describe_skin_types? +

Yes. Add a rate_limit block to the describe_skin_types 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.

How do I block describe_skin_types completely? +

Set action: deny in the PolicyLayer policy for describe_skin_types. 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.

What MCP server provides describe_skin_types? +

describe_skin_types is provided by the D Fetcher MCP server (https://dfetcher.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every D Fetcher tool call.

Deterministic rules across all 3 D Fetcher tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.