AI agents call get_user to retrieve information from Dev To MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information from the dev.to platform without modifying any data or triggering side effects. It is a straightforward query operation that reads and returns publicly available user data, fitting the 'Read' category. The lack of any write, execute, or destructive capability, combined with the public nature of the API and user data, results in low severity.
From the tool's definition Tool name 'get_user' and description 'Get user information by ID or username' indicate retrieval of user profile data.
Documented attack patterns abuse exactly the kind of access get_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dev To MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user:
{
"version": "1",
"default": "deny",
"tools": {
"get_user": {}
}
}get_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get user information by ID or username. It is categorised as a Read tool in the Dev To MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dev To MCP Server MCP server in PolicyLayer and add a rule for get_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 Dev To MCP Server. Nothing to install.
get_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_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_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_user is provided by the Dev To MCP Server MCP server (nickytonline/dev-to-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Dev To MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Dev To MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.