View your Shortlist profile summary including personal details, skills, work experience, and completion status.
AI agents call get_profile to retrieve information from Shortlist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns profile information. There are no side effects, data modifications, deletions, code executions, or financial implications. The blast radius of misuse is minimal—an attacker could view the user's profile data but cannot alter, delete, or take damaging actions with this tool alone.
From the tool's definition Tool name 'get_profile' and description 'View your Shortlist profile summary including personal details, skills, work experience, and completion status' explicitly retrieves and displays existing user data without modification or external actions.
Documented attack patterns abuse exactly the kind of access get_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shortlist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_profile": {}
}
} get_profile 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.
View your Shortlist profile summary including personal details, skills, work experience, and completion status. It is categorised as a Read tool in the Shortlist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for get_profile: 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 Shortlist MCP Server. Nothing to install.
get_profile 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_profile 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_profile. 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_profile is provided by the Shortlist MCP Server MCP server (mls-tech-inc/shortlistjobs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shortlist 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.
32 Shortlist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.