workboard_get_user_key_results_tool
AI agents call workboard_get_user_key_results_tool to retrieve information from MCP Workboard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves key results information about a user with no indication of mutation, deletion, or execution capabilities. The 'get' prefix and absence of write/delete/execute language classify it as a Read operation. No side effects are evident.
From the tool's definition Tool name contains 'get_user_key_results' — the 'get' verb indicates a retrieval operation. The tool fetches key results data for a user, consistent with query/read semantics.
Attacks that exploit this kind of access
workboard_get_user_key_results_tool. It is categorised as a Read tool in the MCP Workboard MCP Server, which means it retrieves data without modifying state.
Register the MCP Workboard MCP server in PolicyLayer and add a rule for workboard_get_user_key_results_tool: 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 MCP Workboard. Nothing to install.
workboard_get_user_key_results_tool 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 workboard_get_user_key_results_tool 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 workboard_get_user_key_results_tool. 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.
workboard_get_user_key_results_tool is provided by the MCP Workboard MCP server (mcp-workboard-crunchtools). 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 →