High Risk →

ojp_parse_job_posting

Produce a structured OJP extraction template from raw job posting text. Returns a document skeleton with _EXTRACT_* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information commonly missing from postings. The calling agent should fill in the skeleton using i...

Part of the Opentalentprotocol MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke ojp_parse_job_posting to trigger processes or run actions in Opentalentprotocol. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

ojp_parse_job_posting can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-testinat0r-otp-ojp.yaml
tools:
  ojp_parse_job_posting:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Opentalentprotocol policy for all 6 tools.

Tool Name ojp_parse_job_posting
Category Execute
Risk Level High

Agents calling execute-class tools like ojp_parse_job_posting have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

ojp_parse_job_posting is one of the high-risk operations in Opentalentprotocol. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the ojp_parse_job_posting tool do? +

Produce a structured OJP extraction template from raw job posting text. Returns a document skeleton with _EXTRACT_* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information commonly missing from postings. The calling agent should fill in the skeleton using its reasoning over the text, then call ojp_validate_job_posting to verify the result.. It is categorised as a Execute tool in the Opentalentprotocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ojp_parse_job_posting? +

Add a rule in your Intercept YAML policy under the tools section for ojp_parse_job_posting. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Opentalentprotocol MCP server.

What risk level is ojp_parse_job_posting? +

ojp_parse_job_posting is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ojp_parse_job_posting? +

Yes. Add a rate_limit block to the ojp_parse_job_posting rule in your Intercept 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.

How do I block ojp_parse_job_posting completely? +

Set action: deny in the Intercept policy for ojp_parse_job_posting. 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.

What MCP server provides ojp_parse_job_posting? +

ojp_parse_job_posting is provided by the Opentalentprotocol MCP server (@opentalentprotocol/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Opentalentprotocol

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.