setup_profile · Nutrition MCP: Risk & Policy

WHAT IT DOES

What setup_profile does on Nutrition MCP

AI agents use setup_profile to create or update resources in Nutrition MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nutrition MCP environment.

WHY IT NEEDS A POLICY

Why setup_profile needs a policy

This tool creates or initializes user profile data, which is a Write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or retrieve data (not Read). The severity is low because creating a profile has minimal security impact—it's a foundational, reversible operation with no destructive or financial consequences.

From the tool's definition Tool description states it creates ('Create the nutrition tracking profile'), which is a reversible data modification operation. The profile is a configuration entity that can be updated or reset.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_profile Rate-limited

setup_profile stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_profile": {
      "limits": [
        {
          "counter": "setup_profile_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nutrition MCP, so you can run agents against it safely.

FAQ

Questions about setup_profile

What does the setup_profile tool do? +

Create the nutrition tracking profile used for daily goals and timezone-aware logging. It is categorised as a Write tool in the Nutrition MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_profile? +

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

What risk level is setup_profile? +

setup_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_profile? +

Yes. Add a rate_limit block to the setup_profile 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 setup_profile completely? +

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

setup_profile is provided by the Nutrition MCP server (ronkommoji/nutrition-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.