AI agents call trw_skill_discovery to retrieve information from Trw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name suggests discovering or querying available skills/capabilities, which implies a read/query operation. However, the description is empty, making classification uncertain. 'Discovery' typically implies a read-like operation (listing, querying, fetching). Confidence is low due to lack of description.
From the tool's definition Tool name 'trw_skill_discovery' — no description provided.
Attacks that exploit this kind of access
trw_skill_discovery. It is categorised as a Read tool in the Trw MCP Server, which means it retrieves data without modifying state.
Register the Trw MCP server in PolicyLayer and add a rule for trw_skill_discovery: 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 Trw. Nothing to install.
trw_skill_discovery 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 trw_skill_discovery 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 trw_skill_discovery. 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.
trw_skill_discovery is provided by the Trw MCP server (wallter/trw-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 →