Assess whether a job posting contains scam risk signals.
AI agents call check_job_posting_legitimacy to retrieve information from RecruiterCheck MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads job posting data and evaluates it against scam-detection criteria, returning analytical results. There are no side effects, data modifications, code execution, deletions, or financial transactions. The blast radius of misuse is minimal—an agent could submit irrelevant postings for analysis, but this would only waste resources and return analysis results without harm to systems or data.
From the tool's definition Tool name 'check_job_posting_legitimacy' and description 'Assess whether a job posting contains scam risk signals' indicate the tool retrieves and analyzes data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Assess whether a job posting contains scam risk signals. It is categorised as a Read tool in the RecruiterCheck MCP MCP Server, which means it retrieves data without modifying state.
Register the RecruiterCheck MCP server in PolicyLayer and add a rule for check_job_posting_legitimacy: 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 RecruiterCheck MCP. Nothing to install.
check_job_posting_legitimacy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_job_posting_legitimacy 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 check_job_posting_legitimacy. 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.
check_job_posting_legitimacy is provided by the RecruiterCheck MCP server (jesslbrown/recruitercheck-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →