query_erp

Answers a natural-language ERP question by planning a safe read-only MySQL query, executing it, and summarizing the results.

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nitrostack/query-erp.md

WHAT IT DOES

What query_erp does on Nitrostack

AI agents call query_erp to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why query_erp is rated Low

Tool retrieves data via read-only queries with no modification or deletion capabilities.

From the tool's definition safe read-only MySQL query, summarizing results

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_erp safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_erp, this is the rule to start with:

query_erp Allowed

query_erp is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_erp": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every query_erp call is checked against it from then on.

FAQ

Questions about query_erp

What does the query_erp tool do? +

Answers a natural-language ERP question by planning a safe read-only MySQL query, executing it, and summarizing the results. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_erp? +

Register the Nitrostack MCP server in PolicyLayer and add a rule for query_erp: 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 Nitrostack. Nothing to install.

What risk level is query_erp? +

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

Can I rate-limit query_erp? +

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

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

query_erp is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →