complete_intake · Pelaris MCP: Risk & Policy

WHAT IT DOES

What complete_intake does on Pelaris

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

WHY IT NEEDS A POLICY

Why complete_intake needs a policy

The tool appears to initialize or complete an athlete intake form/profile, which is a reversible data creation operation. This fits the Write category. Severity is medium because misuse could lead to profile pollution or incorrect athlete data being used for coaching recommendations, but it doesn't delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial).

From the tool's definition Tool name 'complete_intake' and context of 'athlete' profile completion within a fitness coaching platform suggests creating or modifying user profile data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_intake Rate-limited

complete_intake 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": {
    "complete_intake": {
      "limits": [
        {
          "counter": "complete_intake_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 Pelaris, so you can run agents against it safely.

FAQ

Questions about complete_intake

What does the complete_intake tool do? +

Complete the athlete. It is categorised as a Write tool in the Pelaris MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_intake? +

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

What risk level is complete_intake? +

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

Can I rate-limit complete_intake? +

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

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

complete_intake is provided by the Pelaris MCP server (thedonk/pelaris-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.