Get string details by hashcode
AI agents call smartling_get_string_details 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 retrieves string metadata/details from the Smartling translation management system. The 'get' operation and the passive language ('Get string details') indicate a query-only action that returns existing data without creating, modifying, deleting, or executing anything. No side effects are expected from retrieving translation string information.
From the tool's definition Tool name includes 'get' and description states 'Get string details by hashcode', which are read operations that retrieve information without modification or side effects.
Attacks that exploit this kind of access
Get string details by hashcode. 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_get_string_details: 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_get_string_details 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_get_string_details 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_get_string_details. 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_get_string_details 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 →