AI agents use import_tool_config to create or update resources in Msty Admin MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Msty Admin MCP environment.
Importing a tool configuration modifies the system state by adding or updating configuration data. This is a Write operation as it creates or alters configurations reversibly. Severity is high because misconfigured tools could degrade system functionality, affect AI model behavior, or expose unintended capabilities.
From the tool's definition Tool name 'import_tool_config' and description 'Import tool configuration' indicates creation or modification of tool configurations in the Msty Admin system.
Documented attack patterns abuse exactly the kind of access import_tool_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Msty Admin MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for import_tool_config:
{
"version": "1",
"default": "deny",
"tools": {
"import_tool_config": {
"limits": [
{
"counter": "import_tool_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_tool_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Import tool configuration. It is categorised as a Write tool in the Msty Admin MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Msty Admin MCP server in PolicyLayer and add a rule for import_tool_config: 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 Msty Admin MCP. Nothing to install.
import_tool_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_tool_config 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 import_tool_config. 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.
import_tool_config is provided by the Msty Admin MCP server (m-pineapple/msty-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Msty Admin MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Msty Admin MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.