analyze_salary_by_location_and_skills
AI agents call analyze_salary_by_location_and_skills to retrieve information from VisiData MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to perform analytical queries on salary data grouped by location and skills. Analysis and benchmarking operations typically retrieve and compute statistics without modifying underlying data. Sibling analysis tools on the server are clearly Read category.
From the tool's definition Tool name 'analyze_salary_by_location_and_skills' combined with server description mentioning 'salary benchmarking' and 'analysis' features.
Attacks that exploit this kind of access
analyze_salary_by_location_and_skills. It is categorised as a Read tool in the VisiData MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VisiData MCP Server MCP server in PolicyLayer and add a rule for analyze_salary_by_location_and_skills: 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 VisiData MCP Server. Nothing to install.
analyze_salary_by_location_and_skills 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 analyze_salary_by_location_and_skills 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 analyze_salary_by_location_and_skills. 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.
analyze_salary_by_location_and_skills is provided by the VisiData MCP Server MCP server (moeloubani/visidata-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 →