Skip to main content
Verdent provides multiple ways to customize behavior and extend capabilities to match your workflow and security requirements.

​
What You’ll Learn

  • Configure permissions and deny rules
  • Customize behavior through rule systems
  • Extend capabilities with MCP integration
  • Combine methods for comprehensive workflows

​
Extensibility Overview

MethodBest ForConfiguration
PermissionsBlock dangerous commandsSettings → Permissions
User RulesPersonal coding preferencesSettings → User Rules
Project RulesTeam conventionsAGENTS.md in project root
MCP IntegrationExternal tools and servicesSettings → MCP Servers

​
Permissions

Configure command permissions and security rules in Settings → Permissions.

​
Deny Rules

Deny rules prevent potentially dangerous commands from being executed. Verdent blocks most dangerous commands by default, but you can add additional rules. Access: Settings → Permissions → Deny Rules Enter one rule per line. Deny rules take precedence over allow rules. Rule Syntax:
  • Use * as a wildcard to match any characters
  • Rules are case-sensitive
  • Each line represents a separate rule
  • Empty lines are ignored
Common Patterns:
PatternPurpose
rm -rf /*Prevent recursive deletion from root
curl * | *sh*Block piping downloaded scripts to shell
dd * of=/dev/sd*Prevent disk overwrite operations
When Verdent attempts to execute a command that matches a deny rule, it will be blocked for your safety.

​
Rules System

Rule files guide Verdent’s behavior, output formatting, and adherence to project standards.
Rule TypeScopeAccess
User RulesGlobal (all projects)Settings → User Rules
Project RulesCurrent projectAGENTS.md in project root
Precedence: AGENTS.md (highest) → user_rules.md (medium) → defaults (lowest)

​
User Rules

Personal preferences applied across all projects. Access: Settings → User Rules Example: 
# User Rules

## TypeScript Preferences
- Use strict mode in tsconfig.json
- Prefer interfaces over type aliases
- Include return types on all functions

## Code Organization
- One component per file
- Named exports instead of default exports

## Communication
- Provide explanations before showing code
- Highlight breaking changes explicitly

​
Project Rules (AGENTS.md)

Team standards for the current project. Store in project root and commit to version control. Example: 
# AGENTS.md

## Dev Environment
- Run `pnpm install` to set up
- Use `pnpm dev` for local development

## Testing
- Run `pnpm test` before committing
- Minimum 80% coverage required

## PR Guidelines
- Use conventional commit format
- Include tests for new features

​
Rule Precedence

When conflicts occur, project rules override user rules: 
user_rules.md: "Use 2-space indentation"
AGENTS.md: "Use 4-space indentation for this project"
→ Result: 4-space indentation (project rules win)

​
Rule Writing Best Practices

Be Specific and Directive: 
✓ Good: "Always use async/await for asynchronous operations"
✗ Vague: "Try to use modern JavaScript"
Tips:
  • Group related rules under section headers
  • Use emphasis for critical rules: **NEVER** commit credentials
  • Start new conversation to verify rule application
  • Refine rules based on actual agent behavior
Commit AGENTS.md to version control to share rules across your team.

​
MCP Integration

Model Context Protocol (MCP) extends Verdent by connecting external tools and services. Configuration: Settings → MCP Servers

​
Capabilities

CategoryExamples
DatabasesPostgreSQL, MySQL, MongoDB
Cloud ServicesAWS, Azure, GCP
Project ManagementJira, Linear, Asana
CI/CDGitHub Actions, Jenkins

​
@-Mentionable MCP Servers

Custom MCP servers can be invoked using @-mentions, enabling specialized workflows: 
@migration-reviewer check this database migration
@api-security-auditor review this endpoint
@a11y-auditor validate accessibility
Learn More:

​
Combining Methods

​
Example: Compliance Workflow

AGENTS.md (Project Rules): 
## Security Standards
- All API endpoints must validate inputs
- Never log PII or credentials

## Compliance
- Run @compliance-auditor before all PRs
- Document data retention policies
MCP Integration:
  • Compliance database MCP: Check operations against compliance rules
  • Audit log MCP: Record sensitive data access
Workflow: 
User: "Create endpoint for user profile updates"
Verdent: [Applies AGENTS.md rules]
         [Generates secure endpoint with validation]
         [Uses @compliance-auditor MCP for review]
         Result: Compliant, secure endpoint

​
Progressive Adoption

Phase 1: Start with basic rules (AGENTS.md) Phase 2: Add MCP servers for external integrations Phase 3: Create custom MCP servers for specialized tasks

​
Choosing the Right Method

NeedMethod
Block dangerous commandsPermissions (Deny Rules)
Personal coding preferencesUser Rules
Team conventionsProject Rules (AGENTS.md)
External service accessMCP Integration
Specialized AI reviewCustom MCP Server (@-mentionable)

​
Troubleshooting

Problem: Rules not being appliedCheck:
  • Location: AGENTS.md in project root, User Rules in Settings
  • Syntax: Valid Markdown with no parsing errors
  • Directive Style: Use specific commands (“Always use…” not “Try to…”)
  • Session: Start new conversation to test fresh rule application
Common Causes:
  • AGENTS.md in wrong directory
  • Vague instructions
  • Rules applied but results not as expected (refine wording)

​
FAQs

Go to Settings → Permissions → Deny Rules. Enter one pattern per line using * as a wildcard.
Yes. Deny rules always take precedence over allow rules.
Go to Settings → User Rules to define personal preferences that apply across all projects.
Yes. Custom MCP servers can be invoked using @-mentions (e.g., @migration-reviewer).

​
See Also

Rule Systems

Complete rules documentation

Integration Workflows

MCP integration patterns

Settings

All configuration options

Tool Reference

Built-in tool capabilities