AI agents call get_user_history to retrieve information from Doctranslate Io 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 fetch user history records without modifying or deleting data. Though the description is empty (lowering confidence slightly), the name clearly indicates a retrieval operation consistent with Read category functions. No evidence of side effects, code execution, financial transactions, or destructive operations.
From the tool's definition Tool name 'get_user_history' suggests retrieving historical data; description is empty but the naming convention and sibling tools (translation-focused) indicate a data retrieval function with no modification capability.
Documented attack patterns abuse exactly the kind of access get_user_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doctranslate Io MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_history": {}
}
}get_user_history 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.
get_user_history. It is categorised as a Read tool in the Doctranslate Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Doctranslate Io MCP Server MCP server in PolicyLayer and add a rule for get_user_history: 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 Doctranslate Io MCP Server. Nothing to install.
get_user_history 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_user_history 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_user_history. 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_user_history is provided by the Doctranslate Io MCP Server MCP server (thinkprompt/doctranslateio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Doctranslate Io 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.
5 Doctranslate Io MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.