# apply_to_job Launch the LLM-driven job application for a private apply-agent instance: the PAGS agent drives the user Agent View of the PolicyLayer registry record for `apply_to_job`. HTML page: https://policylayer.com/tools/io-github-proagentstore-platform/apply-to-job ## Facts - Tool: `apply_to_job` - Server: ProAgentStore (`https://mcp.proagentstore.online/mcp`) — https://policylayer.com/tools/io-github-proagentstore-platform.md - Homepage: https://github.com/ProAgentStore/platform - Risk category: Execute (High risk) - Registry record: grade D, identity unverified - Server auth posture: gated - 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": "apply_to_job", "arguments": {} } } ``` ## Why apply_to_job is rated High This tool triggers an automated, LLM-driven external operation (submitting a job application on behalf of the user). It initiates an agent-driven workflow with real-world effects (applying for a job), which constitutes executing an external operation. It could also have financial or reputational consequences, but the primary classification is Execute since it drives an automated process. From the tool's own definition: "'Launch the LLM-driven job application for a private apply-agent instance: the PAGS agent drives the user'" ## Use case AI agents invoke apply_to_job to trigger actions in ProAgentStore. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ProAgentStore: ```json { "version": "1", "default": "deny", "tools": { "apply_to_job": { "limits": [ { "counter": "apply_to_job_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on ProAgentStore (242) - `cancel_instance_task` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/cancel-instance-task.md - `clear_finished_tasks` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/clear-finished-tasks.md - `clear_instance_messages` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/clear-instance-messages.md - `clear_instance_voice_settings` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/clear-instance-voice-settings.md - `coding_loop_queue_cancel` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/coding-loop-queue-cancel.md - `coding_repo_remove` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/coding-repo-remove.md - `delete_agent` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-agent.md - `delete_agent_knowledge` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-agent-knowledge.md - `delete_agent_task` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-agent-task.md - `delete_connection` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-connection.md - `delete_feedback` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-feedback.md - `delete_instance_connector_grant` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-connector-grant.md - `delete_instance_file` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-file.md - `delete_instance_knowledge` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-knowledge.md - `delete_instance_memory` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-memory.md - `delete_instance_message` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-message.md - `delete_instance_task` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-task.md - `delete_instance_trigger` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-instance-trigger.md - `delete_supervision` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/delete-supervision.md - `forget_runner_node` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/forget-runner-node.md - `remove_repo` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/remove-repo.md - `unregister_instance_runtime` — Destructive — https://policylayer.com/tools/io-github-proagentstore-platform/unregister-instance-runtime.md - `answer_instance_input` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/answer-instance-input.md - `answer_instance_mcp_input_request` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/answer-instance-mcp-input-request.md - `approve_instance_task` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/approve-instance-task.md - `call_instance_tool` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/call-instance-tool.md - `chat_with_agent` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/chat-with-agent.md - `chat_with_instance` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/chat-with-instance.md - `coding_engine_reauth` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/coding-engine-reauth.md - `coding_loop_start` — Execute — https://policylayer.com/tools/io-github-proagentstore-platform/coding-loop-start.md - …and 212 more: https://policylayer.com/tools/io-github-proagentstore-platform.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=io-github-proagentstore-platform · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-proagentstore-platform