server-mcp

The code uses `exec` to dynamically create function prototypes from introspected Python function signatures or Pydantic models. While `exec` is generally a high-risk function, its usage here appears to be controlled internally for AST manipulation based on validated inputs, rather than arbitrary user-controlled code execution. Resource functions, if implemented by users to accept arbitrary file paths from client input, could introduce path traversal vulnerabilities; however, the provided examples use hardcoded paths, making them safe within the example context. The server also relies on dynamically loaded plugins via `entry_points`, meaning the overall security posture is also dependent on the trustworthiness of any installed plugins. No hardcoded secrets were identified.