This record as markdown: /tools/cutpilot/read-export-job.md
What read_export_job does on Cutpilot
AI agents call read_export_job to retrieve information from Cutpilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_export_job is rated Low
This tool queries the state of an export job without creating, modifying, deleting, or executing any operations. It is a simple data retrieval operation that returns information about an existing export job. The 'read' prefix and verb in the description confirm the Read category. Severity is low because retrieving job metadata poses minimal risk—it cannot alter system state or trigger unexpected processes.
From the tool's definition Tool name contains 'read_' prefix and description states 'Read one persistent export job' — explicitly a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs read_export_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_export_job, this is the rule to start with:
read_export_job 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 Cutpilot, apply this rule, and every read_export_job call is checked against it from then on.
Questions about read_export_job
Read one persistent export job. It is categorised as a Read tool in the Cutpilot MCP Server, which means it retrieves data without modifying state.
Register the Cutpilot MCP server in PolicyLayer and add a rule for read_export_job: 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 Cutpilot. Nothing to install.
read_export_job 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 read_export_job 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 read_export_job. 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.
read_export_job is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
This server
Across the catalogue