AI agents call security_scan to retrieve information from Entroly Context Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A security_scan tool in the context of a codebase analysis engine most likely performs static analysis or scanning of code for vulnerabilities—a read operation that retrieves security information without modifying systems.
From the tool's definition Tool name 'security_scan' and context of an analysis/optimization engine suggests information gathering and analysis rather than modification or execution.
Documented attack patterns abuse exactly the kind of access security_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Entroly Context Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for security_scan:
{
"version": "1",
"default": "deny",
"tools": {
"security_scan": {}
}
}security_scan 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.
security_scan. It is categorised as a Read tool in the Entroly Context Engine MCP Server, which means it retrieves data without modifying state.
Register the Entroly Context Engine MCP server in PolicyLayer and add a rule for security_scan: 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 Entroly Context Engine. Nothing to install.
security_scan 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 security_scan 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 security_scan. 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.
security_scan is provided by the Entroly Context Engine MCP server (juyterman1000/entroly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Entroly Context Engine, 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.
52 Entroly Context Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.