This record as markdown: /tools/mcp-dev/get-member.md
What get-member does on Mcp Dev
AI agents call get-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 get-member is rated Low
This tool retrieves member information by identifier. It performs a read-only lookup with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker gains access to member profile data but cannot change or destroy it. Severity is low because read operations on user data in a CMS context are generally lower risk than write, execute, or destructive operations.
From the tool's definition Tool name is 'get-member' and description states 'Gets a member by Id' — a straightforward query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get-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 get-member, this is the rule to start with:
get-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 get-member call is checked against it from then on.
Questions about get-member
Gets a member by Id. 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 get-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.
get-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 get-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 get-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.
get-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