AI agents call discussion_get to retrieve information from Lockstep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves discussion threads and their messages, which is a read-only operation. It queries data from the coordination system but does not create, modify, delete, or execute any operations. The low severity reflects minimal risk even if misused—an agent retrieving discussion threads cannot damage systems, execute code, or cause financial harm.
From the tool's definition Tool name 'discussion_get' and description 'Get a discussion thread with all its messages' indicate retrieval of existing data without modification or side effects.
Attacks that exploit this kind of access
Get a discussion thread with all its messages. It is categorised as a Read tool in the Lockstep MCP Server, which means it retrieves data without modifying state.
Register the Lockstep MCP server in PolicyLayer and add a rule for discussion_get: 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 Lockstep. Nothing to install.
discussion_get 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 discussion_get 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 discussion_get. 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.
discussion_get is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). 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 →