get_account_info

Retrieve bot account details: name, URI, icon, subscriber count, webhook URL, and subscribed event types. Use to verify bot configuration or check subscriber count. No parameters required. Returns full account configuration object.

Server Viber serhiizghama/viber-mcp
Category Read
Risk class Low
Parameters 00 required

What get_account_info does on Viber

AI agents call get_account_info 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.

Why get_account_info needs a policy

This is a straightforward informational read operation. It queries bot configuration and metrics without modifying, deleting, or triggering external actions. The tool has no parameters and only returns existing data about the bot account. Severity is low because exposure would only leak bot metadata, not compromise user data or enable destructive actions.

From the tool's definition Tool retrieves account details (name, URI, icon, subscriber count, webhook URL, event types) with 'No parameters required' and returns 'full account configuration object'.

Questions about get_account_info

What does the get_account_info tool do? +

Retrieve bot account details: name, URI, icon, subscriber count, webhook URL, and subscribed event types. Use to verify bot configuration or check subscriber count. No parameters required. Returns full account configuration object. It is categorised as a Read tool in the Viber MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_info? +

Register the Viber MCP server in PolicyLayer and add a rule for get_account_info: 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.

What risk level is get_account_info? +

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

Can I rate-limit get_account_info? +

Yes. Add a rate_limit block to the get_account_info 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 get_account_info completely? +

Set action: deny in the PolicyLayer policy for get_account_info. 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 get_account_info? +

get_account_info 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.