10 tools. 8 can modify or destroy data without limits.
7 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry verified 11/06/2026
Running more than one server? Check your whole stack →
8 of MiniMax MCP JS's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and MiniMax MCP JS, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"generate_video": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"list_voices": {
"limits": [
{
"counter": "list_voices_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Free to start. No card required.
Yes. The MiniMax MCP JS server exposes 7 financial tools including generate_video, image_to_video, music_generation. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
10 tools across 2 categories: Read, Write. 2 are read-only. 8 can modify, create, or delete data.
Register the MiniMax MCP JS MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 10 MiniMax MCP JS tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 MiniMax MCP JS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.