list_experience
AI agents call list_experience to retrieve information from Nima Career without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or enumerate career experience data from a curated, public-safe repository. The 'list_' prefix combined with the read-only nature of sibling tools, and the server's stated purpose of exposing pre-approved material, indicates no data modification, deletion, or side effects. Confidence is slightly reduced (0.85 vs 0.95) due to the empty description, but the context is very clear.
From the tool's definition Tool name 'list_experience' indicates a listing/retrieval operation. Sibling tools include 'list_*' variants (list_bullets, list_projects, list_roles, list_skills) which are all read operations retrieving curated career data.
Attacks that exploit this kind of access
list_experience. It is categorised as a Read tool in the Nima Career MCP Server, which means it retrieves data without modifying state.
Register the Nima Career MCP server in PolicyLayer and add a rule for list_experience: 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 Nima Career. Nothing to install.
list_experience 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_experience 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_experience. 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_experience is provided by the Nima Career MCP server (nima-karami/nima-career-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 →