chorus_submit · Facturx MCP: Risk & Policy

WHAT IT DOES

What chorus_submit does on Facturx

AI agents use chorus_submit to create or update resources in Facturx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Facturx environment.

WHY IT NEEDS A POLICY

Why chorus_submit needs a policy

An AI agent can call chorus_submit faster than any human can review — one bad instruction and it creates or modifies resources in Facturx by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chorus_submit Rate-limited

chorus_submit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chorus_submit": {
      "limits": [
        {
          "counter": "chorus_submit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Facturx, so you can run agents against it safely.

FAQ

Questions about chorus_submit

What does the chorus_submit tool do? +

Soumet une facture Factur-X sur la plateforme Chorus Pro (obligatoire pour facturer l\. It is categorised as a Write tool in the Facturx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chorus_submit? +

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

What risk level is chorus_submit? +

chorus_submit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit chorus_submit? +

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

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

chorus_submit is provided by the Facturx MCP server (samdreamsmaker/facturx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.