Find all bounded contexts in the codebase
AI agents call find_bounded_contexts to retrieve information from MCP Code Analysis Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that queries and returns information about code structure (bounded contexts from domain-driven design analysis). It has no side effects, does not execute code, and does not modify data. The blast radius of misuse is minimal—an agent can at worst retrieve structural information about the codebase but cannot cause harm through discovery alone.
From the tool's definition Tool name 'find_bounded_contexts' and description 'Find all bounded contexts in the codebase' indicate a search/discovery operation that retrieves and lists domain-driven design concepts from code without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access find_bounded_contexts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Analysis Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_bounded_contexts:
{
"version": "1",
"default": "deny",
"tools": {
"find_bounded_contexts": {}
}
}find_bounded_contexts 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.
Find all bounded contexts in the codebase. It is categorised as a Read tool in the MCP Code Analysis Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Analysis Server MCP server in PolicyLayer and add a rule for find_bounded_contexts: 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 MCP Code Analysis Server. Nothing to install.
find_bounded_contexts 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 find_bounded_contexts 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 find_bounded_contexts. 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.
find_bounded_contexts is provided by the MCP Code Analysis Server MCP server (johannhartmann/mcpcodeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Code Analysis 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.
44 MCP Code Analysis Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.