24 tools from the Aifp MCP Server, categorised by risk level.
View the Aifp policy →ai_interaction_log Log user corrections and learning data 3/5 categories Manage directive groupings 3/5 directive_dependencies Manage required packages and environment vars 4/5 directive_executions Record directive execution statistics 3/5 directive_flow Configure directive navigation and routing 4/5 directive_helpers Map directives to helper functions 4/5 directive_implementations Link directives to generated code files 4/5 directive_preferences Override per-directive behaviour settings 4/5 directives Manage FP, project, and user preference directives 4/5 fp_flow_tracking Track FP compliance history 3/5 helper_functions Manage database, file, Git, and FP utilities 4/5 infrastructure Manage project setup (language, packages, testing) 4/5 issue_reports Create contextual bug reports 3/5 logging_config Configure file-based logging 3/5 merge_history Track merge conflict resolution audit trail 3/5 notes Add runtime log entries with directive context 2/5 project Manage project metadata and status 4/5 source_files Track user directive source files 3/5 tracking_settings Toggle opt-in tracking feature flags 4/5 types Manage algebraic data types 4/5 user_directives Define directive triggers, actions, and config 5/5 user_settings Configure project-wide AI behaviour settings 4/5 work_branches Manage Git collaboration metadata 4/5 The Aifp MCP server exposes 24 tools across 2 categories: Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Aifp server.
Aifp tools are categorised as Write (23), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept