get_nexus_status
Check sales tax nexus status across US states. Shows revenue and transaction counts per state, flagging states approaching economic nexus thresholds. Uses Stripe payment data.
This record as markdown: /tools/app-businys-mcp-server/get-nexus-status.md
What get_nexus_status does on Businys
AI agents call get_nexus_status to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_nexus_status is rated Low
The tool performs read-only operations: checking status, showing revenue, and flagging thresholds. No data is created, modified, deleted, or executed. However, the sensitivity is elevated (medium rather than low) because it aggregates and exposes financial transaction details and revenue information that could be misused if accessed by an unauthorized agent, though the blast radius is contained to information…
From the tool's definition Tool description states it 'Check[s] sales tax nexus status' and 'Shows revenue and transaction counts per state' — retrieval and querying of existing data with no modification.
Attacks that exploit this kind of access
The rule that runs get_nexus_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_nexus_status, this is the rule to start with:
get_nexus_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every get_nexus_status call is checked against it from then on.
Questions about get_nexus_status
Check sales tax nexus status across US states. Shows revenue and transaction counts per state, flagging states approaching economic nexus thresholds. Uses Stripe payment data. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_nexus_status: 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 Businys. Nothing to install.
get_nexus_status 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 get_nexus_status 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 get_nexus_status. 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.
get_nexus_status is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue