Medium Risk

save_profile

Save the user's travel profile locally for future sessions. Call this after asking the user for their details (name, date of birth, reduction card). Data is stored at ~/.sbb-mcp/profile.json.

Part of the Sbb server.

save_profile can modify Sbb data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SBB →

Free to start. No card required.

AI agents use save_profile to create or modify resources in Sbb. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call save_profile repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Sbb.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_profile": {
      "limits": [
        {
          "counter": "save_profile_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Sbb policy for all 9 tools.

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

ENFORCE ON MY SBB →

View all 9 tools →

These attack patterns abuse exactly the kind of access save_profile 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 save_profile only ever does what you allow.

SECURE SBB →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the save_profile tool do? +

Save the user's travel profile locally for future sessions. Call this after asking the user for their details (name, date of birth, reduction card). Data is stored at ~/.sbb-mcp/profile.json.. It is categorised as a Write tool in the Sbb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_profile? +

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

What risk level is save_profile? +

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

Can I rate-limit save_profile? +

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

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

save_profile is provided by the Sbb MCP server (fabsforward2-zhoi/sbb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sbb tool call.

Deterministic rules across all 9 Sbb 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.