Unsubscribes the authenticated user from job alerts for a specific job search. Input: - job_search_id: The job search identifier to unsubscribe from (required). Accepts either the job search UUID or the composite job ID returned by jobs_search / jobs_details (format: "seo_id--job_search_id"). Out...
Part of the FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT server.
Free to start. No card required.
AI agents call job_alert_unsubscribe to retrieve information from FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though job_alert_unsubscribe only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"job_alert_unsubscribe": {}
}
}See the full FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT policy for all 13 tools.
These attack patterns abuse exactly the kind of access job_alert_unsubscribe gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Unsubscribes the authenticated user from job alerts for a specific job search. Input: - job_search_id: The job search identifier to unsubscribe from (required). Accepts either the job search UUID or the composite job ID returned by jobs_search / jobs_details (format: "seo_id--job_search_id"). Output: Confirms the alert has been unsubscribed. Idempotent: returns success even when the user was not subscribed or is already unsubscribed.. It is categorised as a Read tool in the FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT MCP Server, which means it retrieves data without modifying state.
Register the FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT MCP server in PolicyLayer and add a rule for job_alert_unsubscribe: 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 FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT. Nothing to install.
job_alert_unsubscribe 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 job_alert_unsubscribe 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 job_alert_unsubscribe. 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.
job_alert_unsubscribe is provided by the FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT MCP server (@foundrole/ai-job-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT 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.