Scrape all 6 job sources (SimplifyJobs, RemoteOK, The Muse, Remotive, Jobicy, Arbeitnow), apply 4-gate filter, score, and store. Returns per-source breakdown.
AI agents invoke fetch_jobs to trigger actions in Local Tech Digest. 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.
This tool actively scrapes 6 external job sources (network requests to external services), processes the results, and stores them locally. It is not a passive read — it executes an automated pipeline involving external HTTP operations and data persistence. The most severe applicable category is Execute due to the triggered external operations, though it also has a Write component (storing results).
From the tool's definition 'Scrape all 6 job sources... apply 4-gate filter, score, and store' — triggers external scraping operations across multiple websites and writes results to storage
Attacks that exploit this kind of access
Scrape all 6 job sources (SimplifyJobs, RemoteOK, The Muse, Remotive, Jobicy, Arbeitnow), apply 4-gate filter, score, and store. Returns per-source breakdown. It is categorised as a Execute tool in the Local Tech Digest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Local Tech Digest MCP server in PolicyLayer and add a rule for fetch_jobs: 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 Local Tech Digest. Nothing to install.
fetch_jobs 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 fetch_jobs 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 fetch_jobs. 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.
fetch_jobs is provided by the Local Tech Digest MCP server (nk1947-sudo/local-tech-digest-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 →