setup_credentials · Diabetes:M MCP Server MCP: Risk & Policy

WHAT IT DOES

What setup_credentials does on Diabetes:M MCP Server

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

WHY IT NEEDS A POLICY

Why setup_credentials needs a policy

This tool writes sensitive credentials to a user's profile, which is a reversible but consequential operation. While not destructive (credentials can be changed/cleared via check_credentials and clear_credentials), it modifies persistent authentication state and could allow unauthorized access if misused.

From the tool's definition Tool name 'setup_credentials' and description 'Configure Diabetes:M login credentials' indicate this creates or modifies stored authentication data. The mention of encrypted storage in user profile confirms data persistence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_credentials Rate-limited

setup_credentials 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_credentials": {
      "limits": [
        {
          "counter": "setup_credentials_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 Diabetes:M MCP Server, so you can run agents against it safely.

FAQ

Questions about setup_credentials

What does the setup_credentials tool do? +

Configure Diabetes:M login credentials. Credentials are encrypted and stored securely in your user profile - never in plain text or config files. It is categorised as a Write tool in the Diabetes:M MCP Server 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_credentials? +

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

What risk level is setup_credentials? +

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

Can I rate-limit setup_credentials? +

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

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

setup_credentials is provided by the Diabetes:M MCP Server MCP server (sedoglia/diabetes-m-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.