bolsa_users-lifecycle_change
Change user status (Admin only)
This record as markdown: /tools/cargoffer-bolsa-de-carga-mcp/bolsa-users-lifecycle-change.md
What bolsa_users-lifecycle_change does on Bolsa De Carga
AI agents use bolsa_users-lifecycle_change to create or update resources in Bolsa De Carga, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bolsa De Carga environment.
Why bolsa_users-lifecycle_change is rated Medium
This tool creates or modifies user account status (write operation) rather than reading, executing arbitrary code, or destructively deleting. The blast radius is high because changing user status could lock accounts, revoke access, or escalate privileges if misused by a compromised admin context, but the operation remains reversible (e.g., status can be re-enabled).
From the tool's definition 'Change user status (Admin only)' — modifies user account state, a reversible but significant operation on user lifecycle data. The 'Admin only' restriction indicates elevated privilege required.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs bolsa_users-lifecycle_change safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bolsa De Carga, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bolsa_users-lifecycle_change, this is the rule to start with:
bolsa_users-lifecycle_change 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Bolsa De Carga, apply this rule, and every bolsa_users-lifecycle_change call is checked against it from then on.
Questions about bolsa_users-lifecycle_change
Change user status (Admin only). It is categorised as a Write tool in the Bolsa De Carga MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bolsa De Carga MCP server in PolicyLayer and add a rule for bolsa_users-lifecycle_change: 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 Bolsa De Carga. Nothing to install.
bolsa_users-lifecycle_change is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bolsa_users-lifecycle_change 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.
Set action: deny in the PolicyLayer policy for bolsa_users-lifecycle_change. 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.
bolsa_users-lifecycle_change is provided by the Bolsa De Carga MCP server (cargoffer/bolsa_de_carga-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bolsa De Carga, and thousands of servers like it.
This server
Across the catalogue