get_users
AI agents call get_users to retrieve information from Freelo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_users' semantically indicates data retrieval. There is no evidence of modification, deletion, or execution of external operations. Even without a description, the verb 'get' combined with 'users' clearly points to a query/fetch operation. Confidence is slightly reduced due to the missing description, but the name is sufficiently clear to classify with reasonable confidence.
From the tool's definition Tool name 'get_users' indicates a retrieval operation with no side effects. No description provided, but the name strongly suggests querying/listing user data.
Attacks that exploit this kind of access
get_users. It is categorised as a Read tool in the Freelo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Freelo MCP Server MCP server in PolicyLayer and add a rule for get_users: 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 Freelo MCP Server. Nothing to install.
get_users 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_users 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_users. 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_users is provided by the Freelo MCP Server MCP server (m-hlpr/freelo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →