Gets list of the current Sitecore jobs.
AI agents call common-get-sitecore-job to retrieve information from SitecoreMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it retrieves or lists current job status/data from the Sitecore system. There are no side effects, no data modification, no code execution triggered by arguments, and no destructive or financial implications. The action is equivalent to a 'get' or 'list' operation, which falls squarely in the Read category.
From the tool's definition Tool name 'common-get-sitecore-job' and description 'Gets list of the current Sitecore jobs' indicate a query operation that retrieves information about running jobs without modification.
Attacks that exploit this kind of access
Gets list of the current Sitecore jobs. It is categorised as a Read tool in the SitecoreMCP MCP Server, which means it retrieves data without modifying state.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-get-sitecore-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 SitecoreMCP. Nothing to install.
common-get-sitecore-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 common-get-sitecore-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 common-get-sitecore-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.
common-get-sitecore-job is provided by the Sitecore MCP server (ramseur/mcp-sitecore-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 →