List all tracked job applications, optionally filtered by status.
AI agents call list_applications to retrieve information from LinkedIn Model Context Protocol (MCP) Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing job application records without side effects. It is clearly a Read operation. Severity is medium rather than low because it exposes personal job application history and potentially sensitive career information, which could be misused if an AI agent over-shares this data or uses it for purposes beyond the user's intent, though the blast radius is limited to information…
From the tool's definition Tool name 'list_applications' and description 'List all tracked job applications, optionally filtered by status' indicate a retrieval operation with filtering capability but no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access list_applications gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Model Context Protocol (MCP) Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_applications:
{
"version": "1",
"default": "deny",
"tools": {
"list_applications": {}
}
}list_applications is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tracked job applications, optionally filtered by status. It is categorised as a Read tool in the LinkedIn Model Context Protocol (MCP) Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Model Context Protocol (MCP) Server MCP server in PolicyLayer and add a rule for list_applications: 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 LinkedIn Model Context Protocol (MCP) Server. Nothing to install.
list_applications 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 list_applications 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 list_applications. 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.
list_applications is provided by the LinkedIn Model Context Protocol (MCP) Server MCP server (rayyan9477/linkedin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn Model Context Protocol (MCP) Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 LinkedIn Model Context Protocol (MCP) Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.