AI agents call training.match as a supporting operation in VulneraMCP workflows.
The description is empty and the tool name 'training.match' does not clearly indicate any read, write, execute, destructive, or financial operation. In the context of a bug bounty platform, it might relate to matching findings against training data or known vulnerability patterns, which would be a Read operation, but confidence is very low due to lack of description.
From the tool's definition Tool name is 'training.match' with an empty description. No actionable information available.
Documented attack patterns abuse exactly the kind of access training.match gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VulneraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for training.match:
{
"version": "1",
"default": "deny",
"tools": {
"training.match": {
"limits": [
{
"counter": "training.match_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}training.match gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
training.match. It is categorised as a Other tool in the VulneraMCP MCP Server, which means it performs auxiliary operations.
Register the Vulnera MCP server in PolicyLayer and add a rule for training.match: 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 VulneraMCP. Nothing to install.
training.match is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the training.match 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 training.match. 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.
training.match is provided by the Vulnera MCP server (telmon95/vulneramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 VulneraMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 VulneraMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.