AI agents call get_module_by_name 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 module information by name, which is a query operation with no side effects. It does not execute, modify, delete, or create any data, nor does it trigger financial transactions. The 'get' verb and retrieval-focused description clearly indicate a Read category classification.
From the tool's definition Tool name 'get_module_by_name' with description 'Get specific module by technical name' indicates a retrieval operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access get_module_by_name 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_module_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_module_by_name": {}
}
}get_module_by_name 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 specific module by technical name. 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_module_by_name: 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_module_by_name 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_module_by_name 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_module_by_name. 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_module_by_name 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.