validate-member-update
Validates member data before updating using the Umbraco API. Use this endpoint to validate member data structure, properties, and business rules before attempting to update an existing member.
This record as markdown: /tools/mcp-dev/validate-member-update.md
What validate-member-update does on Mcp Dev
AI agents call validate-member-update to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why validate-member-update is rated Low
This tool performs validation/inspection of member data against Umbraco API constraints. Validation does not modify, execute external actions, delete, or move money. It retrieves/analyzes data to report conformance, which is a Read operation. Severity is low because validation failure simply prevents bad requests; there is no blast radius from misuse.
From the tool's definition Tool description states it 'Validates member data before updating' — validation is a read-only operation that checks structure and business rules without applying changes.
Attacks that exploit this kind of access
The rule that runs validate-member-update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For validate-member-update, this is the rule to start with:
validate-member-update is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every validate-member-update call is checked against it from then on.
Questions about validate-member-update
Validates member data before updating using the Umbraco API. Use this endpoint to validate member data structure, properties, and business rules before attempting to update an existing member. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for validate-member-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 Mcp Dev. Nothing to install.
validate-member-update is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate-member-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 validate-member-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.
validate-member-update is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue