submit · Acatome Quest MCP: Risk & Policy

WHAT IT DOES

What submit does on Acatome Quest

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

WHY IT NEEDS A POLICY

Why submit needs a policy

The 'submit' tool creates or registers a new paper request (DOI, arXiv, etc.) in the system. This is a Write operation—it modifies state by recording a new submission, though the action is reversible via update/status tools. It is not Destructive (nothing is deleted), Execute (no arbitrary code execution), or Financial.

From the tool's definition Tool named 'submit' in a server that handles paper requests and file submissions. Sibling tools include 'submit_file' and 'update', and the server description mentions 'tools for submission, status, update, and file upload.' The name 'submit' suggests…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit Rate-limited

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": {
    "submit": {
      "limits": [
        {
          "counter": "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 Acatome Quest, so you can run agents against it safely.

FAQ

Questions about submit

What does the submit tool do? +

submit. It is categorised as a Write tool in the Acatome Quest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit? +

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

What risk level is submit? +

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

Can I rate-limit submit? +

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

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

submit is provided by the Acatome Quest MCP server (retospect/acatome-quest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.