Why is user X seeing menu Y? This tool inspects the rich-menu priority chain for a user: 1. Per-user link (line_link_rich_menu_to_user) — overrides everything 2. Account-wide default 3. (LINE OA Manager built menus override API-built ones — silent gotcha!) Args: - user_id: LINE user ID. - oa: opt...
AI agents call line_audit_user_menu to retrieve information from Line Oa Mcp Ultimate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves audit information about which rich menu is assigned to a user and why, following a documented priority chain. It has no side effects—it does not create, modify, delete, execute code, or move money. The function is purely informational, making it a Read operation with low severity risk even if exposed to an AI agent.
From the tool's definition Tool description states it 'inspects the rich-menu priority chain for a user' and 'returns' information about what menu is visible. The verb 'inspects' and 'returns' indicate data retrieval with no modification.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access line_audit_user_menu gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Line Oa Mcp Ultimate, and nothing reaches the server without passing your rules. This is the rule we recommend for line_audit_user_menu:
{
"version": "1",
"default": "deny",
"tools": {
"line_audit_user_menu": {}
}
}line_audit_user_menu 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.
Why is user X seeing menu Y? This tool inspects the rich-menu priority chain for a user: 1. Per-user link (line_link_rich_menu_to_user) — overrides everything 2. Account-wide default 3. (LINE OA Manager built menus override API-built ones — silent gotcha!) Args: - user_id: LINE user ID. - oa: optional OA id. Returns: { user_id, visible_rich_menu_id?: string, source:. It is categorised as a Read tool in the Line Oa Mcp Ultimate MCP Server, which means it retrieves data without modifying state.
Register the Line Oa Mcp Ultimate MCP server in PolicyLayer and add a rule for line_audit_user_menu: 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 Line Oa Mcp Ultimate. Nothing to install.
line_audit_user_menu 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 line_audit_user_menu 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 line_audit_user_menu. 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.
line_audit_user_menu is provided by the Line Oa Mcp Ultimate MCP server (wasintoh/line-oa-mcp-ultimate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Line Oa Mcp Ultimate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
34 Line Oa Mcp Ultimate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.