> ## Documentation Index > Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt > Use this file to discover all available pages before exploring further. # ERM MCP FAQ > Common questions about the allGood ERM MCP: what it can change, publishing, permissions, and approvals. ### Can the ERM MCP change how my live mail is classified? No. It can only edit a **draft** copy of your configuration. Your live configuration keeps handling mail exactly as before until you publish the draft yourself in the allGood web app. There is no tool that publishes. ### Why can't it publish for me? By design. Publishing changes how every inbound reply is handled, so it stays a deliberate human step. The assistant ends each improvement round with a full list of what changed and a pointer to review the draft in the web app. ### Why is my new draft's Test Suite empty? Each version of a configuration has its own Test Suite. A draft starts as a copy of your categories but not your test cases. Ask the assistant to copy your live suite onto the draft before re-running. The [guided workflows](/use-cases/erm-mcp/workflows) do this automatically. ### Can it delete anything? No. It can create and edit test cases, and create and edit a draft, but there are no delete or archive tools. Remove test cases from the [Test Suite](/use-cases/erm/test-suite) page in the web app. ### Does it read my live inbox or send email? No. It doesn't read the Messages list, and running the Test Suite is entirely offline. Nothing is sent to anyone. ### Can I control which actions need my approval first? Yes. Permissions are set per tool, not per connector. In your client's tool permissions settings, each tool can be set to always allow, ask each time, or never allow. A sensible setup: | Tools | Suggested setting | | - | - | | List and get configurations, list test cases, get suite results | Always allow | | Create or update test cases, create a draft, update a draft, run the suite | Ask each time | Admins can set this for the whole workspace. See [Roll out the ERM MCP to your organization](/use-cases/erm-mcp/admin-rollout). ### What permissions do I need? * **View reply management** to look up configurations, test cases, and results * **Manage reply management** to create or update test cases, create or edit drafts, and run the Test Suite The tool settings in your AI client narrow what's available. They never grant more than your allGood role allows. ### The assistant says an edit replaced all my categories. Is that right? Updating a draft replaces its whole list of categories, so the assistant always sends the complete list and changes only what you approved. If a category looks missing, ask the assistant to compare the draft with the live configuration. Your live configuration is unaffected. ### Why does the assistant skip the "Other" category when writing tests? "Other" is a catch-all for anything that doesn't fit, so realistic emails nearly always land in a more specific category, and tests for it tend to be flaky. The assistant notes that it left it uncovered. ### A test failed right after I created it. Does that mean something's wrong? Not necessarily. Either the example email isn't as clear-cut as intended, or the test has found a real gap in a category definition. The assistant flags both so you can decide. ### What's the difference between a failed and an errored test? **Failed** means the model gave a wrong answer. **Errored** means the test couldn't be run properly. If errors persist, contact [allGood support](mailto:support@allgoodhq.com). ### Is every action logged? Yes. Every MCP tool call is logged against the person who made it. Admins can review it at **Settings → MCP Usage**, filterable by user or tool. *** If this doesn't answer your question, contact [allGood support](mailto:support@allgoodhq.com). ## Related articles * [Overview](/use-cases/erm-mcp/index) * [Tool reference](/use-cases/erm-mcp/capabilities) * [Guided workflows](/use-cases/erm-mcp/workflows) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.