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 server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"ojp_parse_job_posting": {
"limits": [
{
"counter": "ojp_parse_job_posting_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} See the full Opentalentprotocol policy for all 6 tools.
These attack patterns abuse exactly the kind of access ojp_parse_job_posting gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Opentalentprotocol MCP server in PolicyLayer and add a rule for ojp_parse_job_posting: 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 Opentalentprotocol. Nothing to install.
ojp_parse_job_posting is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ojp_parse_job_posting 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 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.
ojp_parse_job_posting is provided by the Opentalentprotocol MCP server (@opentalentprotocol/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Opentalentprotocol tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.