Get jobs in the system. Can filtered by q (query to filter job name), deadline_from (Unix timestamp in seconds), deadline_to (Unix timestamp in seconds), created_from (Unix timestamp in seconds), created_to (Unix timestamp in seconds), finish_from (Unix timestamp in seconds), finish_to (Unix time...
AI agents call get_jobs to retrieve information from Rework MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves job records using various filter criteria (query, timestamps, user names, workflow ID, status). There are no modifications, deletions, command executions, or financial implications. The filtering parameters are all input constraints for querying existing data, not operations that change state.
From the tool's definition Tool name is 'get_jobs' and description states 'Get jobs in the system' with filtering parameters only. No create, modify, delete, or execute operations are mentioned. The tool retrieves and queries existing job data with no side effects.
Attacks that exploit this kind of access
Get jobs in the system. Can filtered by q (query to filter job name), deadline_from (Unix timestamp in seconds), deadline_to (Unix timestamp in seconds), created_from (Unix timestamp in seconds), created_to (Unix timestamp in seconds), finish_from (Unix timestamp in seconds), finish_to (Unix timestamp in seconds), page (page number), creator_username (username of creator), username (username of assignee), q (query to filter job name), workflow_id (ID of the workflow that the jobs belong to), status (one of:. It is categorised as a Read tool in the Rework MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rework MCP Server MCP server in PolicyLayer and add a rule for get_jobs: 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 Rework MCP Server. Nothing to install.
get_jobs 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_jobs 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_jobs. 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_jobs is provided by the Rework MCP Server MCP server (rework-com/rework-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →