List all contexts in the project
AI agents call smartling_list_contexts to retrieve information from Smartling MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns context data from a Smartling project without modifying, creating, or deleting any information. It is a simple read operation that retrieves existing project metadata. The blast radius of misuse is minimal—an unauthorized listing of contexts would at worst expose metadata about the project structure, but cannot directly harm data or operations.
From the tool's definition Tool name 'list_contexts' and description 'List all contexts in the project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all contexts in the project. It is categorised as a Read tool in the Smartling MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_list_contexts: 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 Smartling MCP Server. Nothing to install.
smartling_list_contexts 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 smartling_list_contexts 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 smartling_list_contexts. 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.
smartling_list_contexts is provided by the Smartling MCP Server MCP server (jacobolevy/smartling-mcp-server). 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 →