users-get

Get a specific user by ID

SERVERFrontmcp SOURCEagentfront/frontmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/users-get.md

WHAT IT DOES

What users-get does on Frontmcp

AI agents call users-get to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why users-get is rated Low

This tool retrieves user data by ID, which is a straightforward query operation. It has no capability to modify, delete, or execute actions. The blast radius is limited to information disclosure of a single user record. Severity is low because retrieval of user data alone (unless highly sensitive PII is involved) typically poses minimal risk when accessed appropriately.

From the tool's definition Tool name 'users-get' and description 'Get a specific user by ID' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs users-get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users-get, this is the rule to start with:

users-get Allowed

users-get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "users-get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every users-get call is checked against it from then on.

FAQ

Questions about users-get

What does the users-get tool do? +

Get a specific user by ID. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on users-get? +

Register the Front MCP server in PolicyLayer and add a rule for users-get: 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 Frontmcp. Nothing to install.

What risk level is users-get? +

users-get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit users-get? +

Yes. Add a rate_limit block to the users-get 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.

How do I block users-get completely? +

Set action: deny in the PolicyLayer policy for users-get. 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.

What MCP server provides users-get? +

users-get is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →