// MCP TOOL REFERENCE

CODEVIRA MCP TOOLS

48 tools from the Codevira MCP MCP Server, categorised by risk level.

// ALL 48 CODEVIRA MCP TOOLS

READ 28 tools

Read reflect v3.1.0 M8: Build the source context + rendered prompt for an Read check_conflict Check whether a proposed decision contradicts any Read consensus_check v3.1.0 M6 Phase B: Scan decisions written since this IDE Read consensus_status v3.1.0 M6: Return the count of pending cross-IDE conflicts + Read get_code Get the full source of a single function or class by name. Read get_history Get recent decisions touching a file. Default: 5 with truncated context Read get_impact Get the blast radius for a file before modifying it. Read get_node Get the context graph node for a file. Returns a SUMMARY by default Read get_phase Get full details of any phase by number — completed, current, or upcoming. Read get_playbook Get curated architectural rules for a specific task type. Read get_reflections v3.1.0 M8: Top-K most recent reflections (newest first). Read get_roadmap Get current project state: phase number, name, status, next action, Read get_session_context Single Read get_signature Get the skeleton of a Python file — all public function and class names, Read get_skill v3.1.0 M3: Composite-ranked search over active skills. Read get_working_context v3.1.0 M2: Compact markdown rendering of the top working-memory Read list_decisions v2.1.2 Item 11: enumerate decisions with filters (since_date, Read list_reflections v3.1.0 M8: Filtered reflection list. Read list_skills v3.1.0 M3: Filtered list of skills. status= Read list_tags v2.1.2 Item 27: enumerate all tags in the project with decision Read origin_of v3.1.0 M7: Return the M1 origin block attached to a decision Read query_graph Query the function-level call graph. Find callers, callees, tests, or dependents Read search_decisions Search past decisions across sessions and roadmap phases Read spatial_affordances v3.1.0 M4: Return the affordance keys (task_types) applicable Read spatial_heat v3.1.0 M4: Top-K most-touched files in a time window by Read spatial_nearby v3.1.0 M4: Files topologically near a given file, ranked by Read spatial_neighborhood v3.1.0 M4: Return the neighborhood id + members for a file. Read working_get v3.1.0 M2: Top-K live working-memory entries by decay score

WRITE 20 tools

Write consensus_propose_supersession v3.1.0 M7 Phase C: Open a cross-IDE supersession proposal. Write defer_phase Move an upcoming phase to the deferred list. Write reaffirm_decision v3.2.0: refresh a do_not_revert decision Write record_skill v3.1.0 M3: Author a new skill in the canonical store Write refresh_graph Auto-generate context graph nodes for new or unregistered files. Write supersede_decision v2.1.2 Item 26: retire ``old_id`` and link to a replacement. Write supersede_skill v3.1.0 M3: Version a skill. Writes a new skill that supersedes Write add_phase Add a new upcoming phase to the roadmap. Write apply_skill_outcome v3.1.0 M3: Manually record one outcome for a skill — success Write bulk_import_phases v2.1.2 Item 29: backfill multiple historical phases at once. Write complete_phase Mark the current phase as complete and advance to the next upcoming phase. Write consensus_resolve v3.1.0 M7 Phase C: Approve, reject, or withdraw a pending Write promote_skill_to_playbook v3.1.0 M3: Write the skill Write record_decision Record one architectural decision. Set do_not_revert=true to Write set_decision_flag v3.0.0 lightweight flag/tag update for an existing decision. Write update_next_action Update the roadmap Write update_phase_status Update the current phase status: pending | in_progress | blocked. Write working_add v3.1.0 M2: Append one observation or goal to working memory Write working_promote v3.1.0 M2: Promote a working-memory entry to long-term memory Write write_session_log Write a structured session log to .agents/logs/YYYY-MM-DD/.

// FAQ

How many tools does the Codevira MCP MCP server have? +

The Codevira MCP MCP server exposes 48 tools across 2 categories: Read, Write.

How do I enforce policies on Codevira MCP tools? +

Route the Codevira MCP server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Codevira MCP tools fall into? +

Codevira MCP tools are categorised as Read (28), Write (20). Each category has a recommended default policy.

Enforce policy on every Codevira MCP tool call.

Start from Codevira MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.