get-item-user
Gets user items for selection lists and pickers
This record as markdown: /tools/mcp-dev/get-item-user.md
What get-item-user does on Mcp Dev
AI agents call get-item-user 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-item-user is rated Low
This tool retrieves user items for UI selection purposes. It performs a read-only query operation with no capability to modify, execute, or delete data. The narrow scope (populating selection lists) and read-only nature warrant low severity classification.
From the tool's definition Tool description states 'Gets user items for selection lists and pickers' - uses 'Gets' which indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get-item-user 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-item-user, this is the rule to start with:
get-item-user 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-item-user call is checked against it from then on.
Questions about get-item-user
Gets user items for selection lists and pickers. 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-item-user: 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-item-user 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-item-user 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-item-user. 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-item-user 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