AI agents call container_settings_list to retrieve information from Piwik PRO MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves container settings without side effects. The '_list' pattern consistently indicates read-only retrieval across the sibling tools shown (analytics_annotations_list, analytics_custom_dimensions_list). While the description is empty, the naming convention and functional role in a configuration management context strongly suggest this fetches and returns settings data only.
From the tool's definition Tool name 'container_settings_list' indicates a list/retrieval operation with no modification capability. The suffix '_list' is a strong indicator of query-only behavior. Server context shows this is part of Piwik PRO analytics configuration management.
Documented attack patterns abuse exactly the kind of access container_settings_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Piwik PRO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for container_settings_list:
{
"version": "1",
"default": "deny",
"tools": {
"container_settings_list": {}
}
}container_settings_list 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.
container_settings_list. It is categorised as a Read tool in the Piwik PRO MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Piwik PRO MCP Server MCP server in PolicyLayer and add a rule for container_settings_list: 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 Piwik PRO MCP Server. Nothing to install.
container_settings_list 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 container_settings_list 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 container_settings_list. 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.
container_settings_list is provided by the Piwik PRO MCP Server MCP server (piwikpro/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Piwik PRO MCP Server, 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.
66 Piwik PRO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.