Get detailed information about a workflow run.
AI agents call wes_get_run_log to retrieve information from NGS360 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 and queries existing workflow run log data without modifying, creating, deleting, or executing anything. It has no side effects and poses minimal security risk—the blast radius is limited to information disclosure based on access controls. Classified as Read with low severity.
From the tool's definition Tool name 'wes_get_run_log' and description 'Get detailed information about a workflow run' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of accessing log information confirm this is a query/read operation.
Attacks that exploit this kind of access
Get detailed information about a workflow run. It is categorised as a Read tool in the NGS360 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for wes_get_run_log: 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 NGS360 MCP Server. Nothing to install.
wes_get_run_log 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 wes_get_run_log 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 wes_get_run_log. 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.
wes_get_run_log is provided by the NGS360 MCP Server MCP server (ngs360/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 →