Fetch profile details of a Viber user: name, avatar URL, country, language, API version, and device type. Use to personalise messages or verify user identity. Rate-limited to 2 calls per user per 12 hours — cache results when possible. Returns user profile object.
AI agents call get_user_details to retrieve information from Viber 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 Viber API without creating, modifying, deleting, or executing operations. It is purely informational. The rate limiting and caching guidance confirms it is a read operation.
From the tool's definition Tool name 'get_user_details' and description 'Fetch profile details' with 'Returns user profile object' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch profile details of a Viber user: name, avatar URL, country, language, API version, and device type. Use to personalise messages or verify user identity. Rate-limited to 2 calls per user per 12 hours — cache results when possible. Returns user profile object. It is categorised as a Read tool in the Viber MCP Server, which means it retrieves data without modifying state.
Register the Viber MCP server in PolicyLayer and add a rule for get_user_details: 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 Viber. Nothing to install.
get_user_details 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_details 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_details. 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_details is provided by the Viber MCP server (serhiizghama/viber-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 →