validate-member
Validates member data before creation using the Umbraco API. Use this endpoint to validate member data structure, properties, and business rules before attempting to create a new member.
This record as markdown: /tools/mcp-dev/validate-member.md
What validate-member does on Mcp Dev
AI agents call validate-member 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 is rated Low
The tool performs validation (a check/read operation) on member data before creation. It queries the state of data and enforces business rules without creating, modifying, or deleting any records. This is a non-destructive, informational operation that retrieves validation results.
From the tool's definition Tool name 'validate-member' and description states it 'Validates member data before creation' and is used to 'validate member data structure, properties, and business rules' — these are read/check operations with no side effects or data modification.
Attacks that exploit this kind of access
The rule that runs validate-member 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, this is the rule to start with:
validate-member 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 call is checked against it from then on.
Questions about validate-member
Validates member data before creation using the Umbraco API. Use this endpoint to validate member data structure, properties, and business rules before attempting to create a new 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: 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 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 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. 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 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