AI agents call get_modules to retrieve information from PrestaShop MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries module information from a PrestaShop store without creating, modifying, deleting, or executing code. It is a straightforward read operation with minimal security risk, as it only exposes existing module metadata that does not require special access controls in typical e-commerce environments.
From the tool's definition Tool name 'get_modules' and description 'Get PrestaShop modules' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_modules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PrestaShop MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_modules:
{
"version": "1",
"default": "deny",
"tools": {
"get_modules": {}
}
}get_modules 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.
Get PrestaShop modules. It is categorised as a Read tool in the PrestaShop MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PrestaShop MCP Server MCP server in PolicyLayer and add a rule for get_modules: 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 PrestaShop MCP Server. Nothing to install.
get_modules 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 get_modules 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 get_modules. 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.
get_modules is provided by the PrestaShop MCP Server MCP server (latinogino/prestashop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PrestaShop 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.
34 PrestaShop MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.