AI agents call export_tool_config to retrieve information from Msty Admin MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a configuration reads and outputs the current tool configuration data. This is a read/retrieval operation with no side effects. Severity is low as it may expose configuration details but causes no modifications. Confidence is moderate because 'export' could theoretically involve writing to a file, but the primary action is retrieving/exporting data.
From the tool's definition Export Msty tool configuration
Documented attack patterns abuse exactly the kind of access export_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 export_tool_config:
{
"version": "1",
"default": "deny",
"tools": {
"export_tool_config": {}
}
}export_tool_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export Msty tool configuration. It is categorised as a Read tool in the Msty Admin MCP MCP Server, which means it retrieves data without modifying state.
Register the Msty Admin MCP server in PolicyLayer and add a rule for export_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.
export_tool_config 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 export_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 export_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.
export_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.