> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads.md). # Agentic Development Security (ADS) How Agentic Development Security secures the AI agents that build your software Agentic Development Security (ADS) secures the AI agents that build software. AI coding assistants and development agents pull in external tools, take actions across systems, and generate code. ADS secures three parts of that activity: what agents use, what they do, and what they generate. ## What ADS secures * **Agent Supply Chain Security** secures what agents use. It evaluates the components your agents connect to - the Model Context Protocol (MCP) servers, skills, and external tools they use - before those components enter your development workflow. It discovers the components in use on end users' machines across your environment and assesses each one for security issues such as prompt injection, tool poisoning, and hardcoded secrets. * **Agent Behavior Governance** secures what agents do. It works inside the agent execution loop, evaluating an agent's actions against policy before they run, with awareness of the full session: the sequence of actions, the tools in use, and the intent behind them. * **Trusted Output Assurance**, also known as Snyk Studio, secures agent-generated output at creation. It runs inside the coding assistant. Hooks trigger the scanning and fixing of AI-generated code as it gets generated. This catches and fixes vulnerabilities and insecure dependencies before the code reaches a repository. Learn more about [Agentic security with Snyk Studio](https://docs.snyk.io/agent-security). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.