Medium Risk

profile_update_roles

Update the user's role lists in roles.json. Pass any of `detected`, `custom`, `excluded` to replace that list, or `addCustom`/`addExcluded`/`removeCustom`/`removeExcluded` to mutate incrementally. Returns the updated roles plus the computed activeRoles (detected ∪ custom − excluded).

Part of the Jobsync MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

jobsync-mcp Write

AI agents use profile_update_roles to create or modify resources in Jobsync. 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 profile_update_roles repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Jobsync.

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

jobsync.yaml
tools:
  profile_update_roles:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Jobsync policy for all 21 tools.

Tool Name profile_update_roles
Category Write
MCP Server Jobsync MCP Server
Risk Level Medium

View all 21 tools →

Agents calling write-class tools like profile_update_roles have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the profile_update_roles tool do? +

Update the user's role lists in roles.json. Pass any of `detected`, `custom`, `excluded` to replace that list, or `addCustom`/`addExcluded`/`removeCustom`/`removeExcluded` to mutate incrementally. Returns the updated roles plus the computed activeRoles (detected ∪ custom − excluded).. It is categorised as a Write tool in the Jobsync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on profile_update_roles? +

Add a rule in your Intercept YAML policy under the tools section for profile_update_roles. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Jobsync MCP server.

What risk level is profile_update_roles? +

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

Can I rate-limit profile_update_roles? +

Yes. Add a rate_limit block to the profile_update_roles rule in your Intercept 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 profile_update_roles completely? +

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

profile_update_roles is provided by the Jobsync MCP server (jobsync-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.