This record as markdown: /tools/app-businys-mcp-server/training-history.md
What training_history does on Businys
AI agents call training_history to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why training_history is rated Low
This tool retrieves or queries existing training history data without any side effects. The description explicitly frames it as providing background information (read-only access). Given the context of a fitness/training management system, this is a straightforward data retrieval operation that poses minimal security risk if misused by an agent.
From the tool's definition Tool name 'training_history' combined with description 'Brief training background' indicates retrieval of historical training data with no modification capability.
Attacks that exploit this kind of access
The rule that runs training_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For training_history, this is the rule to start with:
training_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every training_history call is checked against it from then on.
Questions about training_history
Brief training background. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for training_history: 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 Businys. Nothing to install.
training_history 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 training_history 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_history. 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_history is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue