This record as markdown: /tools/frontmcp/users-update.md
What users-update does on Frontmcp
AI agents use users-update to create or update resources in Frontmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Frontmcp environment.
Why users-update is rated Medium
This tool modifies user records but does not permanently delete them (which would be Destructive) nor does it execute arbitrary code (which would be Execute). The blast radius depends on what user fields can be modified—if it permits privilege escalation or critical account changes, severity could rise, but 'medium' is appropriate for a standard user data modification without evidence of financial or destructive…
From the tool's definition Tool name 'users-update' and description 'Update an existing user' indicate modification of user data records. This is a reversible write operation that creates or modifies existing data.
Attacks that exploit this kind of access
The rule that runs users-update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users-update, this is the rule to start with:
users-update 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 Frontmcp, apply this rule, and every users-update call is checked against it from then on.
Questions about users-update
Update an existing user. It is categorised as a Write tool in the Frontmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Front MCP server in PolicyLayer and add a rule for users-update: 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 Frontmcp. Nothing to install.
users-update 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 users-update 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 users-update. 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.
users-update is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue