# jobs_get

Get job status and result by jobId. Poll every 20 seconds until status is

Agent View of the PolicyLayer registry record for `jobs_get`. HTML page: https://policylayer.com/tools/2slides-mcp-2slides/jobs-get

## Facts

- Tool: `jobs_get`
- Server: 2slides MCP Server (`2slides/mcp-2slides`) — https://policylayer.com/tools/2slides-mcp-2slides.md
- Homepage: https://github.com/2slides/mcp-2slides
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "jobs_get",
    "arguments": {}
  }
}
```

## Why jobs_get is rated Low

This tool performs a simple status polling operation on an asynchronous job. It retrieves information without modifying, deleting, or executing anything. The worst-case misuse would be repeated polling of job status, which has negligible blast radius and no destructive or financial impact. Classification as Read is appropriate.

From the tool's own definition: "Tool name 'jobs_get' and description 'Get job status and result by jobId' indicate a retrieval operation. The description explicitly states the tool retrieves status information and results, with no side effects—it only queries the state of an existing job."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call jobs_get to retrieve information from 2slides MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 2slides MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "jobs_get": {}
  }
}
```

## Other tools on 2slides MCP Server (6)

- `slides_download_slides_pages_voices` — Read — https://policylayer.com/tools/2slides-mcp-2slides/slides-download-slides-pages-voices.md
- `themes_search` — Read — https://policylayer.com/tools/2slides-mcp-2slides/themes-search.md
- `slides_create_like_this` — Write — https://policylayer.com/tools/2slides-mcp-2slides/slides-create-like-this.md
- `slides_create_pdf_slides` — Write — https://policylayer.com/tools/2slides-mcp-2slides/slides-create-pdf-slides.md
- `slides_generate` — Write — https://policylayer.com/tools/2slides-mcp-2slides/slides-generate.md
- `slides_generate_narration` — Write — https://policylayer.com/tools/2slides-mcp-2slides/slides-generate-narration.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2slides-mcp-2slides · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2slides-mcp-2slides