dock_rescore
A execute tool on the OpenTCM_Discovery MCP server.
This record as markdown: /tools/opentcm-discovery/dock-rescore.md
What dock_rescore does on OpenTCM_Discovery
AI agents invoke dock_rescore to trigger actions in OpenTCM_Discovery. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why dock_rescore is rated High
Tool likely rescores docking results, an execution operation, but description is empty.
From the tool's definition uninformative description
Attacks that exploit this kind of access
The rule that runs dock_rescore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenTCM_Discovery, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dock_rescore, this is the rule to start with:
dock_rescore stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenTCM_Discovery, apply this rule, and every dock_rescore call is checked against it from then on.
Questions about dock_rescore
dock_rescore is a execute tool on the OpenTCM_Discovery MCP server. It is categorised as a Execute tool in the OpenTCM_Discovery MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenTCM_Discovery MCP server in PolicyLayer and add a rule for dock_rescore: 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 OpenTCM_Discovery. Nothing to install.
dock_rescore is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dock_rescore 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 dock_rescore. 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.
dock_rescore is provided by the OpenTCM_Discovery MCP server (S0mbraD/OpenTCM_Discovery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenTCM_Discovery, and thousands of servers like it.
Across the catalogue