# draft_proposal

Draft a customized Upwork proposal based on a job description. Picks the best template (MCP/AI Agent/Discord/General) and writes a custom opening referencing the specific job.

Agent View of the PolicyLayer registry record for `draft_proposal`. HTML page: https://policylayer.com/tools/0xcybin-jobs-mcp/draft-proposal

## Facts

- Tool: `draft_proposal`
- Server: Jobs (`0xcybin/jobs-mcp`) — https://policylayer.com/tools/0xcybin-jobs-mcp.md
- Homepage: https://github.com/0xCybin/jobs-mcp
- Risk category: Write (Medium risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why draft_proposal is rated Medium

This tool generates/creates a proposal document (a write operation), but it appears to only draft content locally without submitting or sending it anywhere. The output is a tailored text proposal. No irreversible actions, financial transactions, or code execution are involved. Severity is low since misuse would at most produce an inappropriate draft proposal.

From the tool's own definition: "Draft a customized Upwork proposal based on a job description. Picks the best template and writes a custom opening referencing the specific job."

## Use case

AI agents use draft_proposal to create or update resources in Jobs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jobs environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Jobs:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "draft_proposal": {
      "limits": [
        {
          "counter": "draft_proposal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Jobs (7)

- `job_scan` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/job-scan.md
- `my_profile` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/my-profile.md
- `search_arbeitnow_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-arbeitnow-jobs.md
- `search_github_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-github-jobs.md
- `search_hn_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-hn-jobs.md
- `search_remote_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-remote-jobs.md
- `search_upwork_jobs` — Read — https://policylayer.com/tools/0xcybin-jobs-mcp/search-upwork-jobs.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=0xcybin-jobs-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xcybin-jobs-mcp