Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, set...
AI agents call how_munimji_helps to retrieve information from HelloBooks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
area | string | — | Optional. Narrow to one business-operation area. |
autonomy | string | — | Optional. Filter Munimji capabilities by who does the work: `autonomous` (Munimji does it alone), `approval` (Munimji prepares, you approve before it posts), `a |
businessDescription | string | — | Optional. The user describes their business and operations in their own words (industry, what they sell, how they get paid, who they pay, tax regime, pain point |
Parameters from the server's own tool schema.
This tool takes a description of a user's business operations and returns informational content about AI capabilities and how they map to that business. It is purely a read/retrieval operation — no data is created, modified, executed, or deleted. It generates a knowledge base response based on input text, with no side effects on any external system or financial data.
From the tool's definition 'Explain how HelloBooks and Munimji help a specific business... Returns a curated capability knowledge base'
Attacks that exploit this kind of access
Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — autonomous (Munimji does it on its own, e.g. OCR extraction, running reports), approval (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), assist (co-pilot, e.g. guided onboarding, voice), or manual (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in businessDescription; optionally filter by area or autonomy. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans. It is categorised as a Read tool in the HelloBooks AI MCP Server MCP Server, which means it retrieves data without modifying state.
how_munimji_helps accepts 3 parameters: area, autonomy, businessDescription. The full parameter table on this page comes from the server's own tool schema.
Register the HelloBooks AI MCP Server MCP server in PolicyLayer and add a rule for how_munimji_helps: 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 HelloBooks AI MCP Server. Nothing to install.
how_munimji_helps 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 how_munimji_helps 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 how_munimji_helps. 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.
how_munimji_helps is provided by the HelloBooks AI MCP Server MCP server (Meru-Fin-Tech/HelloBooks-MCP-Public). 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 →