# find_definition

找出符号在项目中的定义处：函数定义、类定义、模块级/类级赋值（常量、类属性）。

Agent View of the PolicyLayer registry record for `find_definition`. HTML page: https://policylayer.com/tools/0xyubo-ripple-mcp/find-definition

## Facts

- Tool: `find_definition`
- Server: Ripple-MCP (`0xyubo/ripple-mcp`) — https://policylayer.com/tools/0xyubo-ripple-mcp.md
- Homepage: https://github.com/0xYubo/Ripple-Mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_definition",
    "arguments": {}
  }
}
```

## Why find_definition is rated Low

This tool performs static analysis to locate and retrieve information about where symbols are defined in source code. It does not execute code, modify data, delete anything, or move data. It is a read-only query operation that retrieves semantic information from the codebase for impact analysis purposes. The low severity reflects that misuse would only expose code structure information, not cause harm.

From the tool's own definition: "Tool description states it 'finds where a symbol is defined in a project' (function definitions, class definitions, module/class-level assignments)."

## Use case

AI agents call find_definition to retrieve information from Ripple-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Ripple-MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_definition": {}
  }
}
```

## Other tools on Ripple-MCP (5)

- `analyze_python_ast` — Read — https://policylayer.com/tools/0xyubo-ripple-mcp/analyze-python-ast.md
- `generate_impact_report` — Read — https://policylayer.com/tools/0xyubo-ripple-mcp/generate-impact-report.md
- `get_code_context` — Read — https://policylayer.com/tools/0xyubo-ripple-mcp/get-code-context.md
- `scan_patterns` — Read — https://policylayer.com/tools/0xyubo-ripple-mcp/scan-patterns.md
- `trace_callers` — Read — https://policylayer.com/tools/0xyubo-ripple-mcp/trace-callers.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xyubo-ripple-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xyubo-ripple-mcp