Poll the current status of a transcription job by job_id.
AI agents call get_job_status to retrieve information from Whipscribe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves information about a job without modifying, deleting, or executing anything. It is a simple status check that returns job state data. This aligns with the Read category: 'retrieves or queries data; no side effects (search, list, get, fetch).' Severity is low because the blast radius of misuse is minimal—an agent could only poll status information already associated with job IDs it has access to.
From the tool's definition Tool polls and retrieves the status of an existing transcription job—described as 'Get... current status of a transcription job by job_id'. This is a read-only query with no side effects.
Attacks that exploit this kind of access
Poll the current status of a transcription job by job_id. It is categorised as a Read tool in the Whipscribe MCP Server, which means it retrieves data without modifying state.
Register the Whipscribe MCP server in PolicyLayer and add a rule for get_job_status: 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 Whipscribe. Nothing to install.
get_job_status 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_job_status 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_job_status. 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_job_status is provided by the Whipscribe MCP server (neugence/whipscribe-mcp). 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 →