get_unresolved_calls
AI agents call get_unresolved_calls to retrieve information from RobotWS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the context of a Robot Framework metadata indexing server and the analytical nature of sibling tools, 'get_unresolved_calls' most likely retrieves or queries metadata about unresolved function/keyword calls from the SQLite index. This is a Read operation with no side effects.
From the tool's definition Tool name 'get_unresolved_calls' implies retrieval/query of call resolution data. The description is empty, but sibling tools on this server (discover_sg6_features, find_keyword_callers, find_taf_library_usage, evaluate_taf_usage, explain_*) are all…
Attacks that exploit this kind of access
get_unresolved_calls. It is categorised as a Read tool in the RobotWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RobotWS MCP Server MCP server in PolicyLayer and add a rule for get_unresolved_calls: 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 RobotWS MCP Server. Nothing to install.
get_unresolved_calls 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_unresolved_calls 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_unresolved_calls. 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_unresolved_calls is provided by the RobotWS MCP Server MCP server (stella555359/robotws_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 →