Filter stored jobs by domain, type, status, and min score.
AI agents call filter_jobs to retrieve information from Local Tech Digest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters job records based on specified criteria (domain, type, status, score threshold). It performs a query operation with no side effects—no data is created, modified, deleted, or executed. It is a standard Read operation consistent with other sibling tools like 'search_jobs', 'list_new_jobs', and 'fetch_jobs' on the same server.
From the tool's definition Tool name 'filter_jobs' combined with description 'Filter stored jobs by domain, type, status, and min score' indicates retrieval and querying of existing job data with filtering parameters.
Attacks that exploit this kind of access
Filter stored jobs by domain, type, status, and min score. It is categorised as a Read tool in the Local Tech Digest MCP Server, which means it retrieves data without modifying state.
Register the Local Tech Digest MCP server in PolicyLayer and add a rule for filter_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.
filter_jobs 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 filter_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 filter_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.
filter_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 →