# MCP Tool Catalog and Risk Worksheet for ERP Agents > Source: https://netray.co/tools/mcp-tool-catalog-risk-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Register each MCP tool your agent exposes, the ERP object it touches and a computed risk score, then export to Excel. ## Category developer ## Audience - ERP developer - Integration architect - Security reviewer ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Tool name **Key:** tool **Type:** text #### ERP object touched **Key:** erp_object **Type:** text #### Access type **Key:** access **Type:** select **Options:** - Read - Create - Update - Delete - Execute #### Impact if wrong (1-5) **Key:** impact **Type:** number **Help:** 1 = cosmetic, 5 = financial or compliance damage #### Records reachable (1-5) **Key:** reach **Type:** number **Help:** 1 = one record, 5 = whole table or company #### Hard to undo (1-5) **Key:** undo **Type:** number **Help:** 1 = trivially reversible, 5 = irreversible #### Risk score **Key:** risk **Type:** number **Expr:** impact * reach * undo **Format:** integer #### Approval gate **Key:** gate **Type:** select **Options:** - None - Log only - Human approval - Disabled #### Owner **Key:** owner **Type:** text **Rows:** **Tool:** get_open_purchase_orders **Erp object:** Purchase order header and lines **Access:** Read **Impact:** 1 **Reach:** 3 **Undo:** 1 **Gate:** Log only **Owner:** Purchasing **Tool:** get_item_on_hand **Erp object:** Item warehouse balance **Access:** Read **Impact:** 1 **Reach:** 2 **Undo:** 1 **Gate:** None **Owner:** Inventory **Tool:** create_draft_requisition **Erp object:** Purchase requisition **Access:** Create **Impact:** 2 **Reach:** 1 **Undo:** 2 **Gate:** Human approval **Owner:** Purchasing **Tool:** update_promise_date **Erp object:** PO line promise date **Access:** Update **Impact:** 3 **Reach:** 2 **Undo:** 2 **Gate:** Human approval **Owner:** Planning **Tool:** post_goods_receipt **Erp object:** Inventory transaction **Access:** Execute **Impact:** 5 **Reach:** 2 **Undo:** 4 **Gate:** Disabled **Owner:** Warehouse **Tool:** delete_work_order **Erp object:** Work order **Access:** Delete **Impact:** 4 **Reach:** 1 **Undo:** 5 **Gate:** Disabled **Owner:** Production **Totals:** #### Total risk score **Key:** risk **Agg:** sum **Format:** integer #### Highest single tool risk **Key:** risk **Agg:** max **Format:** integer #### Tools registered **Key:** tool **Agg:** count **Format:** integer **Summary:** #### Average risk per tool **Key:** avg_risk **Expr:** sum_risk / count **Format:** decimal **Notes:** Anything scoring above about 40 should sit behind human approval or stay disabled. The scale is a convention for ranking, not a standard. Adjust the gate column after your security review. ## Content **Intro:** An MCP server turns ERP functions into tools an AI model can call. Before any of them ship, you need one register that says what each tool touches, how far a mistake can spread and who approves it. This worksheet is that register, with a computed risk score. **Sections:** #### How to use the worksheet **Body:** List one row per tool exactly as it appears in your MCP server's tool list, using the same name the model sees. Name the ERP object it reads or changes, pick the access type, then score impact, reach and reversibility from 1 to 5. The risk column multiplies the three, so a read-only lookup of one record scores low and a delete across many records scores very high. Set the approval gate last, after the score is visible. Export to Excel and attach the file to your change request or security review. **Bullets:** - One row per tool, never per server - Score the worst realistic mistake, not the expected one - Review the register whenever a tool is added or its parameters change #### How the score works **Body:** The score is impact times reach times reversibility, giving a range of 1 to 125. It is a ranking device borrowed from the way FMEA multiplies severity, occurrence and detection. It is not a standard and the thresholds are yours to set. A common starting rule is: below 10 can run with logging, 10 to 40 needs a human to confirm, above 40 stays disabled until a compensating control exists. Reads are not free: a read tool that can page through every customer record has a high reach even though it changes nothing. #### Reading the example **Body:** In the sample rows, the lookup tools score 2 to 6 and run with light logging. Updating a promise date scores 12 and needs approval because a planner downstream may act on it. Posting a goods receipt scores 40 and deleting a work order scores 20 but is irreversible once downstream transactions exist, so both are marked Disabled until a controlled path exists. The point is that the number forces a conversation about each tool rather than a blanket yes or no on the agent. #### Common mistakes **Body:** Teams often register the MCP server as a single line and approve it as a whole. Others forget that a generic execute-SQL or run-report tool can reach every table, which makes its reach score a 5 regardless of how it is described. Also remember that ERP roles still apply: the service account behind the tool should carry the least privilege that tool needs, and the register should name that account. **Bullets:** - Avoid generic query or script tools unless the reach score is honest - Record the ERP service account per tool - Keep write tools separate from read tools so each can be gated alone **Cta:** Netray builds MCP and agent layers over ERP with read-only defaults and human approval on write-back. If you want a second pair of eyes on your tool register, we can review it. **Faq:** #### How many tools should one MCP server expose? **Answer:** There is no fixed limit, but fewer, well-described tools generally give better model behavior and smaller prompts. Many teams stay under a few dozen per server and split by domain, such as purchasing, inventory and production, so each agent only sees the tools it needs. #### Do read-only tools need approval? **Answer:** Usually not per call, but they still need logging and a reach limit. A read tool that returns every employee or pricing record can leak data without changing anything. Score reach honestly and cap row counts in the tool itself. #### Is the risk score an industry standard? **Answer:** No. It is a simple multiplication in the style of FMEA scoring, offered so you can rank tools and set your own thresholds. Replace it with your organization's own risk matrix if one exists. #### Can I import this into Excel? **Answer:** You can export the worksheet to Excel or CSV with one click. The risk column is exported as values, so if you want live formulas, multiply the three score columns in your spreadsheet. ## Search terms mcp tool inventory, mcp tool catalog template, ai agent tool register excel, mcp server tool list spreadsheet, agent tool risk assessment, erp ai agent tool inventory, mcp tools risk score --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json