Show your job application pipeline grouped by status.
AI agents call get_pipeline 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 queries and displays job application pipeline information organized by status. It performs a read-only operation with no side effects, no data modification, no code execution, and no financial impact. The verb 'Show' confirms it is a data retrieval function. Blast radius is minimal since misuse would only expose the user's own pipeline data visibility.
From the tool's definition Tool name 'get_pipeline' and description 'Show your job application pipeline grouped by status' indicates a retrieval operation that displays existing data without modification or execution of external operations.
Attacks that exploit this kind of access
Show your job application pipeline grouped by status. 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 get_pipeline: 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.
get_pipeline 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 get_pipeline 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 get_pipeline. 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.
get_pipeline 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 →