This record as markdown: /tools/mcp-dev/find-member.md
What find-member does on Mcp Dev
AI agents call find-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 find-member is rated Low
This tool performs a read-only lookup operation on member records in Umbraco CMS. It searches for and retrieves member information based on filter criteria, with no capability to modify, delete, or execute actions. The blast radius of misuse is limited to information disclosure of member data.
From the tool's definition Tool name 'find-member' and description 'Finds members by various filter criteria' indicate a query/search operation that retrieves member data without modification.
Attacks that exploit this kind of access
The rule that runs find-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 find-member, this is the rule to start with:
find-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 find-member call is checked against it from then on.
Questions about find-member
Finds members by various filter criteria. 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 find-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.
find-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 find-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 find-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.
find-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